Data management for an application with multiple operation modes

ABSTRACT

A method and system for managing an application with multiple modes are described. A device manager that manages a mobile device may monitor the mobile device. The device manager may detect that a first type of application that runs in a managed mode (or in multiple managed modes) and an unmanaged mode is installed on the mobile device. When the application is executed on the device, the application executes in accordance with the selected application mode, e.g., based on location, user, role, industry presence, or other predefined context.

CROSS-REFERENCE TO RELATED APPLICATIONS

This application is a continuation of non-provisional application Ser.No. 14/021,227, filed on Sep. 9, 2013, entitled, “Data Management For AnApplication With Multiple Operation Modes,” which claims priority toprovisional application 61/861,736, filed Aug. 2, 2013, entitled“Policy-Based Application Management,” provisional application61/861,758, filed Aug. 2, 2013, entitled “Data Management for anApplication with Multiple Operation Modes,” and provisional application61/806,577, filed Mar. 29, 2013, entitled “Systems and Methods forEnterprise Mobility Management,” and is a continuation-in-part of U.S.patent application Ser. No. 13/886,889, filed May 2, 2013, entitled“Application with Multiple Operation Modes,” each of which is hereinincorporated by reference in its entirety.

BACKGROUND

The use of mobile computing devices continues to grow. In particular,business and other enterprises have come to rely on mobile computingdevices to allow individuals to remotely access various enterpriseresources. Such resources may include, for example, electronic mailservices, file services, data, and other electronic resources providedby the computer systems of an enterprise.

With this insurgence of business use, individuals are beginning to usetheir mobile computing devices in both business and personal ways. Forexample, an employee of a corporation may access a corporate emailaccount and a personal email account from the same mobile computingdevice. Accordingly, certain functionality of a mobile computing devicemay share business and personal aspects. However, business informationoften requires secure communication and storage. Additionally, businessinformation stored on a mobile device may require management. Thus,there is a need for a device manager to manage information stored on amobile device.

SUMMARY

The following presents a simplified summary of various aspects describedherein. This summary is not an extensive overview, and is not intendedto identify key or critical elements or to delineate the scope of theclaims. The following summary merely presents some concepts in asimplified form as an introductory prelude to the more detaileddescription provided below.

A method and system for managing an application with multiple operationmodes are described herein. A device manager that manages a mobiledevice may monitor the mobile device. The device manager may detect thata predetermined type of application that runs in an unmanaged mode and amanaged mode is installed on the mobile device. The operation mode maybe based on a device context or device-related information. For example,the application may run in a first, managed, mode when user credentialsauthenticate a user as a trusted user, and the application may otherwiserun in a second less-secure mode. Operational mode may also be selectedbased on a physical location of the device, a network location, usercredentials, user roles, location types (e.g., healthcare, financialinstitution premises, schools, government entities, etc., also referredto as workplace environment types), and the like. An application may beexecutable in more than two operation modes, and may be executable inmultiple different managed modes providing different levels of access,security, resources, etc.

These and additional aspects will be appreciated with the benefit of thedisclosures discussed in further detail below.

BRIEF DESCRIPTION OF THE DRAWINGS

A more complete understanding of aspects described herein and theadvantages thereof may be acquired by referring to the followingdescription in consideration of the accompanying drawings, in which likereference numbers indicate like features, and wherein:

FIG. 1 depicts an illustrative computer system architecture that may beused in accordance with an illustrative embodiment.

FIG. 2 depicts an illustrative remote-access system architecture thatmay be used in accordance with an illustrative embodiment.

FIG. 3 depicts an illustrative virtualized (hypervisor) systemarchitecture that may be used in accordance with an illustrativeembodiment.

FIG. 4 depicts an illustrative cloud-based system architecture that maybe used in accordance with an illustrative embodiment.

FIG. 5 depicts an illustrative enterprise mobility management systemthat may be used in accordance with an illustrative embodiment.

FIG. 6 depicts another illustrative enterprise mobility managementsystem that may be used in accordance with an illustrative embodiment.

FIG. 7 depicts a sample interface of a mobile device in accordance withan illustrative embodiment.

FIG. 8 is a flowchart for determining an application mode for anapplication in accordance with an illustrative embodiment.

FIG. 9 is a flowchart for determining an account type context for anapplication in accordance with an illustrative embodiment.

FIG. 10 is a flowchart for determining a location context for anapplication in accordance with an illustrative embodiment.

FIG. 11 is a flowchart for determining a predetermine application statuscontext for an application in accordance with an illustrativeembodiment.

FIG. 12 is a flowchart for determining a network connection context foran application in accordance with an illustrative embodiment.

FIG. 13 is a flowchart for determining a settings context for anapplication in accordance with an illustrative embodiment.

FIG. 14 is a flowchart for switching an application mode for anapplication in accordance with an illustrative embodiment.

FIG. 15 is a flowchart for managing an application with multipleoperation modes in accordance with an illustrative embodiment.

FIG. 16 is a flowchart for managing a multi-mode application inaccordance with an illustrative embodiment.

FIG. 17 is a flowchart for an app store in accordance with anillustrative embodiment.

DETAILED DESCRIPTION

In the following description of the various embodiments, reference ismade to the accompanying drawings identified above and which form a parthereof, and in which is shown by way of illustration various embodimentsin which aspects described herein may be practiced. It is to beunderstood that other embodiments may be utilized and structural andfunctional modifications may be made without departing from the scopedescribed herein. Various aspects are capable of other embodiments andof being practiced or being carried out in various different ways.

As a general introduction to the subject matter described in more detailbelow, aspects described herein are directed towards controlling remoteaccess to resources at an enterprise computing system using managedmobile applications at mobile computing devices, specifically as usedwith applications capable of executing in multiple operational modes. Anaccess manager may perform a validation process that determines whethera mobile application requesting access to enterprise resources hasaccurately identified itself and has not been subsequently altered afterinstallation at the mobile computing device. In this way, the accessmanager may ensure the mobile application requesting access to theenterprise resource can be trusted and are not attempting to circumventthe security mechanisms used to protect those enterprise resources. As aresult, individuals associated with the enterprise may advantageouslyutilize enterprise resources at their personal mobile devices usingpreapproved applications.

It is to be understood that the phraseology and terminology used hereinare for the purpose of description and should not be regarded aslimiting. Rather, the phrases and terms used herein are to be giventheir broadest interpretation and meaning. The use of “including” and“comprising” and variations thereof is meant to encompass the itemslisted thereafter and equivalents thereof as well as additional itemsand equivalents thereof. The use of the terms “mounted,” “connected,”“coupled,” “positioned,” “engaged” and similar terms, is meant toinclude both direct and indirect mounting, connecting, coupling,positioning and engaging.

Computing Architecture

Computer software, hardware, and networks may be utilized in a varietyof different system environments, including standalone, networked,remote-access (aka, remote desktop), virtualized, and/or cloud-basedenvironments, among others. FIG. 1 illustrates one example of a systemarchitecture and data processing device that may be used to implementone or more illustrative aspects described herein in a standalone and/ornetworked environment. Various network nodes 103, 105, 107, and 109 maybe interconnected via a wide area network (WAN) 101, such as theInternet. Other networks may also or alternatively be used, includingprivate intranets, corporate networks, LANs, metropolitan area networks(MAN) wireless networks, personal networks (PAN), and the like. Network101 is for illustration purposes and may be replaced with fewer oradditional computer networks. A local area network (LAN) may have one ormore of any known LAN topology and may use one or more of a variety ofdifferent protocols, such as Ethernet. Devices 103, 105, 107, 109 andother devices (not shown) may be connected to one or more of thenetworks via twisted pair wires, coaxial cable, fiber optics, radiowaves or other communication media.

The term “network” as used herein and depicted in the drawings refersnot only to systems in which remote storage devices are coupled togethervia one or more communication paths, but also to stand-alone devicesthat may be coupled, from time to time, to such systems that havestorage capability. Consequently, the term “network” includes not only a“physical network” but also a “content network,” which is comprised ofthe data—attributable to a single entity—which resides across allphysical networks.

The components may include data server 103, web server 105, and clientcomputers 107, 109. Data server 103 provides overall access, control andadministration of databases and control software for performing one ormore illustrative aspects describe herein. Data server 103 may beconnected to web server 105 through which users interact with and obtaindata as requested. Alternatively, data server 103 may act as a webserver itself and be directly connected to the Internet. Data server 103may be connected to web server 105 through the network 101 (e.g., theInternet), via direct or indirect connection, or via some other network.Users may interact with the data server 103 using remote computers 107,109, e.g., using a web browser to connect to the data server 103 via oneor more externally exposed web sites hosted by web server 105. Clientcomputers 107, 109 may be used in concert with data server 103 to accessdata stored therein, or may be used for other purposes. For example,from client device 107 a user may access web server 105 using anInternet browser, as is known in the art, or by executing a softwareapplication that communicates with web server 105 and/or data server 103over a computer network (such as the Internet).

Servers and applications may be combined on the same physical machines,and retain separate virtual or logical addresses, or may reside onseparate physical machines. FIG. 1 illustrates just one example of anetwork architecture that may be used, and those of skill in the artwill appreciate that the specific network architecture and dataprocessing devices used may vary, and are secondary to the functionalitythat they provide, as further described herein. For example, servicesprovided by web server 105 and data server 103 may be combined on asingle server.

Each component 103, 105, 107, 109 may be any type of known computer,server, or data processing device. Data server 103, e.g., may include aprocessor 111 controlling overall operation of the rate server 103. Dataserver 103 may further include RAM 113, ROM 115, network interface 117,input/output interfaces 119 (e.g., keyboard, mouse, display, printer,etc.), and memory 121. I/O 119 may include a variety of interface unitsand drives for reading, writing, displaying, and/or printing data orfiles. Memory 121 may further store operating system software 123 forcontrolling overall operation of the data processing device 103, controllogic 125 for instructing data server 103 to perform aspects describedherein, and other application software 127 providing secondary, support,and/or other functionality which may or might not be used in conjunctionwith aspects described herein. The control logic may also be referred toherein as the data server software 125. Functionality of the data serversoftware may refer to operations or decisions made automatically basedon rules coded into the control logic, made manually by a user providinginput into the system, and/or a combination of automatic processingbased on user input (e.g., queries, data updates, etc.).

Memory 121 may also store data used in performance of one or moreaspects described herein, including a first database 129 and a seconddatabase 131. In some embodiments, the first database may include thesecond database (e.g., as a separate table, report, etc.). That is, theinformation can be stored in a single database, or separated intodifferent logical, virtual, or physical databases, depending on systemdesign. Devices 105, 107, 109 may have similar or different architectureas described with respect to device 103. Those of skill in the art willappreciate that the functionality of data processing device 103 (ordevice 105, 107, 109) as described herein may be spread across multipledata processing devices, for example, to distribute processing loadacross multiple computers, to segregate transactions based on geographiclocation, user access level, quality of service (QoS), etc.

One or more aspects may be embodied in computer-usable or readable dataand/or computer-executable instructions, such as in one or more programmodules, executed by one or more computers or other devices as describedherein. Generally, program modules include routines, programs, objects,components, data structures, etc. that perform particular tasks orimplement particular abstract data types when executed by a processor ina computer or other device. The modules may be written in a source codeprogramming language that is subsequently compiled for execution, or maybe written in a scripting language such as (but not limited to) HTML orXML. The computer executable instructions may be stored on a computerreadable medium such as a nonvolatile storage device. Any suitablecomputer readable storage media may be utilized, including hard disks,CD-ROMs, optical storage devices, magnetic storage devices, and/or anycombination thereof. In addition, various transmission (non-storage)media representing data or events as described herein may be transferredbetween a source and a destination in the form of electromagnetic wavestraveling through signal-conducting media such as metal wires, opticalfibers, and/or wireless transmission media (e.g., air and/or space).Various aspects described herein may be embodied as a method, a dataprocessing system, or a computer program product. Therefore, variousfunctionalities may be embodied in whole or in part in software,firmware and/or hardware or hardware equivalents such as integratedcircuits, field programmable gate arrays (FPGA), and the like.Particular data structures may be used to more effectively implement oneor more aspects described herein, and such data structures arecontemplated within the scope of computer executable instructions andcomputer-usable data described herein.

With further reference to FIG. 2, one or more aspects described hereinmay be implemented in a remote-access environment. FIG. 2 depicts anexample system architecture including a generic computing device 201 inan illustrative computing environment 200 that may be used according toone or more illustrative aspects described herein. Generic computingdevice 201 may be used as a server 206 a in a single-server ormulti-server desktop virtualization system (e.g., a remote access orcloud system) configured to provide virtual machines for client accessdevices. The generic computing device 201 may have a processor 203 forcontrolling overall operation of the server and its associatedcomponents, including random access memory (RAM) 205, read-only memory(ROM) 207, input/output (I/O) module 209, and memory 215.

I/O module 209 may include a mouse, keypad, touch screen, scanner,optical reader, and/or stylus (or other input device(s)) through which auser of generic computing device 201 may provide input, and may alsoinclude one or more of a speaker for providing audio output and a videodisplay device for providing textual, audiovisual, and/or graphicaloutput. Software may be stored within memory 215 and/or other storage toprovide instructions to processor 203 for configuring generic computingdevice 201 into a special purpose computing device in order to performvarious functions as described herein. For example, memory 215 may storesoftware used by the computing device 201, such as an operating system217, application programs 219, and an associated database 221.

Computing device 201 may operate in a networked environment supportingconnections to one or more remote computers, such as terminals 240 (alsoreferred to as client devices). The terminals 240 may be personalcomputers, mobile devices, laptop computers, tablets, or servers thatinclude many or all of the elements described above with respect to thegeneric computing device 103 or 201. The network connections depicted inFIG. 2 include a local area network (LAN) 225 and a wide area network(WAN) 229, but may also include other networks. When used in a LANnetworking environment, computing device 201 may be connected to the LAN225 through a network interface or adapter 223. When used in a WANnetworking environment, computing device 201 may include a modem 227 orother wide area network interface for establishing communications overthe WAN 229, such as computer network 230 (e.g., the Internet). It willbe appreciated that the network connections shown are illustrative andother means of establishing a communications link between the computersmay be used. Computing device 201 and/or terminals 240 may also bemobile terminals (e.g., mobile phones, smartphones, PDAs, notebooks,etc.) including various other components, such as a battery, speaker,and antennas (not shown).

Aspects described herein may also be operational with numerous othergeneral purpose or special purpose computing system environments orconfigurations. Examples of other computing systems, environments,and/or configurations that may be suitable for use with aspectsdescribed herein include, but are not limited to, personal computers,server computers, hand-held or laptop devices, multiprocessor systems,microprocessor-based systems, set top boxes, programmable consumerelectronics, network PCs, minicomputers, mainframe computers,distributed computing environments that include any of the above systemsor devices, and the like.

As shown in FIG. 2, one or more client devices 240 may be incommunication with one or more servers 206 a-206 n (generally referredto herein as “server(s) 206”). In one embodiment, the computingenvironment 200 may include a network appliance installed between theserver(s) 206 and client machine(s) 240. The network appliance maymanage client/server connections, and in some cases can load balanceclient connections amongst a plurality of backend servers 206.

The client machine(s) 240 may in some embodiments be referred to as asingle client machine 240 or a single group of client machines 240,while server(s) 206 may be referred to as a single server 206 or asingle group of servers 206. In one embodiment a single client machine240 communicates with more than one server 206, while in anotherembodiment a single server 206 communicates with more than one clientmachine 240. In yet another embodiment, a single client machine 240communicates with a single server 206.

A client machine 240 can, in some embodiments, be referenced by any oneof the following non-exhaustive terms: client machine(s); client(s);client computer(s); client device(s); client computing device(s); localmachine; remote machine; client node(s); endpoint(s); or endpointnode(s). The server 206, in some embodiments, may be referenced by anyone of the following non-exhaustive terms: server(s), local machine;remote machine; server farm(s), or host computing device(s).

In one embodiment, the client machine 240 may be a virtual machine. Thevirtual machine may be any virtual machine, while in some embodimentsthe virtual machine may be any virtual machine managed by a Type 1 orType 2 hypervisor, for example, a hypervisor developed by CitrixSystems, IBM, VMware, or any other hypervisor. In some aspects, thevirtual machine may be managed by a hypervisor, while in aspects thevirtual machine may be managed by a hypervisor executing on a server 206or a hypervisor executing on a client 240.

Some embodiments include a client device 240 that displays applicationoutput generated by an application remotely executing on a server 206 orother remotely located machine. In these embodiments, the client device240 may execute a virtual machine receiver program or application todisplay the output in an application window, a browser, or other outputwindow. In one example, the application is a desktop, while in otherexamples the application is an application that generates or presents adesktop. A desktop may include a graphical shell providing a userinterface for an instance of an operating system in which local and/orremote applications can be integrated. Applications, as used herein, areprograms that execute after an instance of an operating system (and,optionally, also the desktop) has been loaded.

The server 206, in some embodiments, uses a remote presentation protocolor other program to send data to a thin-client or remote-displayapplication executing on the client to present display output generatedby an application executing on the server 206. The thin-client orremote-display protocol can be any one of the following non-exhaustivelist of protocols: the Independent Computing Architecture (ICA) protocoldeveloped by Citrix Systems, Inc. of Ft. Lauderdale, Fla.; or the RemoteDesktop Protocol (RDP) manufactured by the Microsoft Corporation ofRedmond, Wash.

A remote computing environment may include more than one server 206a-206 n such that the servers 206 a-206 n are logically grouped togetherinto a server farm 206, for example, in a cloud computing environment.The server farm 206 may include servers 206 that are geographicallydispersed while and logically grouped together, or servers 206 that arelocated proximate to each other while logically grouped together.Geographically dispersed servers 206 a-206 n within a server farm 206can, in some embodiments, communicate using a WAN (wide), MAN(metropolitan), or LAN (local), where different geographic regions canbe characterized as: different continents; different regions of acontinent; different countries; different states; different cities;different campuses; different rooms; or any combination of the precedinggeographical locations. In some embodiments the server farm 206 may beadministered as a single entity, while in other embodiments the serverfarm 206 can include multiple server farms.

In some embodiments, a server farm may include servers 206 that executea substantially similar type of operating system platform (e.g.,WINDOWS, UNIX, LINUX, iOS, ANDROID, SYMBIAN, etc.) In other embodiments,server farm 206 may include a first group of one or more servers thatexecute a first type of operating system platform, and a second group ofone or more servers that execute a second type of operating systemplatform.

Server 206 may be configured as any type of server, as needed, e.g., afile server, an application server, a web server, a proxy server, anappliance, a network appliance, a gateway, an application gateway, agateway server, a virtualization server, a deployment server, a SSL VPNserver, a firewall, a web server, an application server or as a masterapplication server, a server executing an active directory, or a serverexecuting an application acceleration program that provides firewallfunctionality, application functionality, or load balancingfunctionality. Other server types may also be used.

Some embodiments include a first server 106 a that receives requestsfrom a client machine 240, forwards the request to a second server 106b, and responds to the request generated by the client machine 240 witha response from the second server 106 b. First server 106 a may acquirean enumeration of applications available to the client machine 240 andwell as address information associated with an application server 206hosting an application identified within the enumeration ofapplications. First server 106 a can then present a response to theclient's request using a web interface, and communicate directly withthe client 240 to provide the client 240 with access to an identifiedapplication. One or more clients 240 and/or one or more servers 206 maytransmit data over network 230, e.g., network 101.

FIG. 2 shows a high-level architecture of an illustrative desktopvirtualization system. As shown, the desktop virtualization system maybe single-server or multi-server system, or cloud system, including atleast one virtualization server 206 configured to provide virtualdesktops and/or virtual applications to one or more client accessdevices 240. As used herein, a desktop refers to a graphical environmentor space in which one or more applications may be hosted and/orexecuted. A desktop may include a graphical shell providing a userinterface for an instance of an operating system in which local and/orremote applications can be integrated. Applications may include programsthat execute after an instance of an operating system (and, optionally,also the desktop) has been loaded. Each instance of the operating systemmay be physical (e.g., one operating system per device) or virtual(e.g., many instances of an OS running on a single device). Eachapplication may be executed on a local device, or executed on a remotelylocated device (e.g., remoted).

With further reference to FIG. 3, a computer device 301 may beconfigured as a virtualization server in a virtualization environment,for example, a single-server, multi-server, or cloud computingenvironment. Virtualization server 301 illustrated in FIG. 3 can bedeployed as and/or implemented by one or more embodiments of the server206 illustrated in FIG. 2 or by other known computing devices. Includedin virtualization server 301 is a hardware layer that can include one ormore physical disks 304, one or more physical devices 306, one or morephysical processors 308 and one or more physical memories 316. In someembodiments, firmware 312 can be stored within a memory element in thephysical memory 316 and can be executed by one or more of the physicalprocessors 308. Virtualization server 301 may further include anoperating system 314 that may be stored in a memory element in thephysical memory 316 and executed by one or more of the physicalprocessors 308. Still further, a hypervisor 302 may be stored in amemory element in the physical memory 316 and can be executed by one ormore of the physical processors 308.

Executing on one or more of the physical processors 308 may be one ormore virtual machines 332A-C (generally 332). Each virtual machine 332may have a virtual disk 326A-C and a virtual processor 328A-C. In someembodiments, a first virtual machine 332A may execute, using a virtualprocessor 328A, a control program 320 that includes a tools stack 324.Control program 320 may be referred to as a control virtual machine,Dom0, Domain 0, or other virtual machine used for system administrationand/or control. In some embodiments, one or more virtual machines 332B-Ccan execute, using a virtual processor 328B-C, a guest operating system330A-B.

Virtualization server 301 may include a hardware layer 310 with one ormore pieces of hardware that communicate with the virtualization server301. In some embodiments, the hardware layer 310 can include one or morephysical disks 304, one or more physical devices 306, one or morephysical processors 308, and one or more memory 216. Physical components304, 306, 308, and 316 may include, for example, any of the componentsdescribed above. Physical devices 306 may include, for example, anetwork interface card, a video card, a keyboard, a mouse, an inputdevice, a monitor, a display device, speakers, an optical drive, astorage device, a universal serial bus connection, a printer, a scanner,a network element (e.g., router, firewall, network address translator,load balancer, virtual private network (VPN) gateway, Dynamic HostConfiguration Protocol (DHCP) router, etc.), or any device connected toor communicating with virtualization server 301. Physical memory 316 inthe hardware layer 310 may include any type of memory. Physical memory316 may store data, and in some embodiments may store one or moreprograms, or set of executable instructions. FIG. 3 illustrates anembodiment where firmware 312 is stored within the physical memory 316of virtualization server 301. Programs or executable instructions storedin the physical memory 316 can be executed by the one or more processors308 of virtualization server 301.

Virtualization server 301 may also include a hypervisor 302. In someembodiments, hypervisor 302 may be a program executed by processors 308on virtualization server 301 to create and manage any number of virtualmachines 332. Hypervisor 302 may be referred to as a virtual machinemonitor, or platform virtualization software. In some embodiments,hypervisor 302 can be any combination of executable instructions andhardware that monitors virtual machines executing on a computingmachine. Hypervisor 302 may be Type 2 hypervisor, where the hypervisorthat executes within an operating system 314 executing on thevirtualization server 301. Virtual machines then execute at a levelabove the hypervisor. In some embodiments, the Type 2 hypervisorexecutes within the context of a user's operating system such that theType 2 hypervisor interacts with the user's operating system. In otherembodiments, one or more virtualization servers 201 in a virtualizationenvironment may instead include a Type 1 hypervisor (Not Shown). A Type1 hypervisor may execute on the virtualization server 301 by directlyaccessing the hardware and resources within the hardware layer 310. Thatis, while a Type 2 hypervisor 302 accesses system resources through ahost operating system 314, as shown, a Type 1 hypervisor may directlyaccess all system resources without the host operating system 314. AType 1 hypervisor may execute directly on one or more physicalprocessors 308 of virtualization server 301, and may include programdata stored in the physical memory 316.

Hypervisor 302, in some embodiments, can provide virtual resources tooperating systems 330 or control programs 320 executing on virtualmachines 332 in any manner that simulates the operating systems 330 orcontrol programs 320 having direct access to system resources. Systemresources can include, but are not limited to, physical devices 306,physical disks 304, physical processors 308, physical memory 316 and anyother component included in virtualization server 301 hardware layer310. Hypervisor 302 may be used to emulate virtual hardware, partitionphysical hardware, virtualize physical hardware, and/or execute virtualmachines that provide access to computing environments. In still otherembodiments, hypervisor 302 controls processor scheduling and memorypartitioning for a virtual machine 332 executing on virtualizationserver 301. Hypervisor 302 may include those manufactured by VMWare,Inc., of Palo Alto, Calif.; the XEN hypervisor, an open source productwhose development is overseen by the open source Xen.org community;HyperV, VirtualServer or virtual PC hypervisors provided by Microsoft,or others. In some embodiments, virtualization server 301 executes ahypervisor 302 that creates a virtual machine platform on which guestoperating systems may execute. In these embodiments, the virtualizationserver 301 may be referred to as a host server. An example of such avirtualization server is the XEN SERVER provided by Citrix Systems,Inc., of Fort Lauderdale, Fla.

Hypervisor 302 may create one or more virtual machines 332B-C (generally332) in which guest operating systems 330 execute. In some embodiments,hypervisor 302 may load a virtual machine image to create a virtualmachine 332. In other embodiments, the hypervisor 302 may executes aguest operating system 330 within virtual machine 332. In still otherembodiments, virtual machine 332 may execute guest operating system 330.

In addition to creating virtual machines 332, hypervisor 302 may controlthe execution of at least one virtual machine 332. In other embodiments,hypervisor 302 may presents at least one virtual machine 332 with anabstraction of at least one hardware resource provided by thevirtualization server 301 (e.g., any hardware resource available withinthe hardware layer 310). In other embodiments, hypervisor 302 maycontrol the manner in which virtual machines 332 access physicalprocessors 308 available in virtualization server 301. Controllingaccess to physical processors 308 may include determining whether avirtual machine 332 should have access to a processor 308, and howphysical processor capabilities are presented to the virtual machine332.

As shown in FIG. 3, virtualization server 301 may host or execute one ormore virtual machines 332. A virtual machine 332 is a set of executableinstructions that, when executed by a processor 308, imitate theoperation of a physical computer such that the virtual machine 332 canexecute programs and processes much like a physical computing device.While FIG. 3 illustrates an embodiment where a virtualization server 301hosts three virtual machines 332, in other embodiments virtualizationserver 301 can host any number of virtual machines 332. Hypervisor 302,in some embodiments, provides each virtual machine 332 with a uniquevirtual view of the physical hardware, memory, processor and othersystem resources available to that virtual machine 332. In someembodiments, the unique virtual view can be based on one or more ofvirtual machine permissions, application of a policy engine to one ormore virtual machine identifiers, a user accessing a virtual machine,the applications executing on a virtual machine, networks accessed by avirtual machine, or any other desired criteria. For instance, hypervisor302 may create one or more unsecure virtual machines 332 and one or moresecure virtual machines 332. Unsecure virtual machines 332 may beprevented from accessing resources, hardware, memory locations, andprograms that secure virtual machines 332 may be permitted to access. Inother embodiments, hypervisor 302 may provide each virtual machine 332with a substantially similar virtual view of the physical hardware,memory, processor and other system resources available to the virtualmachines 332.

Each virtual machine 332 may include a virtual disk 326A-C (generally326) and a virtual processor 328A-C (generally 328.) The virtual disk326, in some embodiments, is a virtualized view of one or more physicaldisks 304 of the virtualization server 301, or a portion of one or morephysical disks 304 of the virtualization server 301. The virtualizedview of the physical disks 304 can be generated, provided and managed bythe hypervisor 302. In some embodiments, hypervisor 302 provides eachvirtual machine 332 with a unique view of the physical disks 304. Thus,in these embodiments, the particular virtual disk 326 included in eachvirtual machine 332 can be unique when compared with the other virtualdisks 326.

A virtual processor 328 can be a virtualized view of one or morephysical processors 308 of the virtualization server 301. In someembodiments, the virtualized view of the physical processors 308 can begenerated, provided and managed by hypervisor 302. In some embodiments,virtual processor 328 has substantially all of the same characteristicsof at least one physical processor 308. In other embodiments, virtualprocessor 308 provides a modified view of physical processors 308 suchthat at least some of the characteristics of the virtual processor 328are different than the characteristics of the corresponding physicalprocessor 308.

With further reference to FIG. 4, some aspects described herein may beimplemented in a cloud-based environment. FIG. 4 illustrates an exampleof a cloud computing environment (or cloud system) 400. As seen in FIG.4, client computers 411-414 may communicate with a cloud managementserver 410 to access the computing resources (e.g., host servers 403,storage resources 404, and network resources 405) of the cloud system.

Management server 410 may be implemented on one or more physicalservers. The management server 410 may run, for example, CLOUDSTACK byCitrix Systems, Inc. of Ft. Lauderdale, Fla., or OPENSTACK, amongothers. Management server 410 may manage various computing resources,including cloud hardware and software resources, for example, hostcomputers 403, data storage devices 404, and networking devices 405. Thecloud hardware and software resources may include private and/or publiccomponents. For example, a cloud may be configured as a private cloud tobe used by one or more particular customers or client computers 411-414and/or over a private network. In other embodiments, public clouds orhybrid public-private clouds may be used by other customers over an openor hybrid networks.

Management server 410 may be configured to provide user interfacesthrough which cloud operators and cloud customers may interact with thecloud system. For example, the management server 410 may provide a setof APIs and/or one or more cloud operator console applications (e.g.,web-based on standalone applications) with user interfaces to allowcloud operators to manage the cloud resources, configure thevirtualization layer, manage customer accounts, and perform other cloudadministration tasks. The management server 410 also may include a setof APIs and/or one or more customer console applications with userinterfaces configured to receive cloud computing requests from end usersvia client computers 411-414, for example, requests to create, modify,or destroy virtual machines within the cloud. Client computers 411-414may connect to management server 410 via the Internet or othercommunication network, and may request access to one or more of thecomputing resources managed by management server 410. In response toclient requests, the management server 410 may include a resourcemanager configured to select and provision physical resources in thehardware layer of the cloud system based on the client requests. Forexample, the management server 410 and additional components of thecloud system may be configured to provision, create, and manage virtualmachines and their operating environments (e.g., hypervisors, storageresources, services offered by the network elements, etc.) for customersat client computers 411-414, over a network (e.g., the Internet),providing customers with computational resources, data storage services,networking capabilities, and computer platform and application support.Cloud systems also may be configured to provide various specificservices, including security systems, development environments, userinterfaces, and the like.

Certain clients 411-414 may be related, for example, different clientcomputers creating virtual machines on behalf of the same end user, ordifferent users affiliated with the same company or organization. Inother examples, certain clients 411-414 may be unrelated, such as usersaffiliated with different companies or organizations. For unrelatedclients, information on the virtual machines or storage of any one usermay be hidden from other users.

Referring now to the physical hardware layer of a cloud computingenvironment, availability zones 401-402 (or zones) may refer to acollocated set of physical computing resources. Zones may begeographically separated from other zones in the overall cloud ofcomputing resources. For example, zone 401 may be a first clouddatacenter located in California, and zone 402 may be a second clouddatacenter located in Florida. Management sever 410 may be located atone of the availability zones, or at a separate location. Each zone mayinclude an internal network that interfaces with devices that areoutside of the zone, such as the management server 410, through agateway. End users of the cloud (e.g., clients 411-414) might or mightnot be aware of the distinctions between zones. For example, an end usermay request the creation of a virtual machine having a specified amountof memory, processing power, and network capabilities. The managementserver 410 may respond to the user's request and may allocate theresources to create the virtual machine without the user knowing whetherthe virtual machine was created using resources from zone 401 or zone402. In other examples, the cloud system may allow end users to requestthat virtual machines (or other cloud resources) are allocated in aspecific zone or on specific resources 403-405 within a zone.

In this example, each zone 401-402 may include an arrangement of variousphysical hardware components (or computing resources) 403-405, forexample, physical hosting resources (or processing resources), physicalnetwork resources, physical storage resources, switches, and additionalhardware resources that may be used to provide cloud computing servicesto customers. The physical hosting resources in a cloud zone 401-402 mayinclude one or more computer servers 403, such as the virtualizationservers 301 described above, which may be configured to create and hostvirtual machine instances. The physical network resources in a cloudzone 401 or 402 may include one or more network elements 405 (e.g.,network service providers) comprising hardware and/or softwareconfigured to provide a network service to cloud customers, such asfirewalls, network address translators, load balancers, virtual privatenetwork (VPN) gateways, Dynamic Host Configuration Protocol (DHCP)routers, and the like. The storage resources in the cloud zone 401-402may include storage disks (e.g., solid state drives (SSDs), magnetichard disks, etc.) and other storage devices.

The example cloud computing environment shown in FIG. 4 also may includea virtualization layer (e.g., as shown in FIGS. 1-3) with additionalhardware and/or software resources configured to create and managevirtual machines and provide other services to customers using thephysical resources in the cloud. The virtualization layer may includehypervisors, as described above in FIG. 3, along with other componentsto provide network virtualizations, storage virtualizations, etc. Thevirtualization layer may be as a separate layer from the physicalresource layer, or may share some or all of the same hardware and/orsoftware resources with the physical resource layer. For example, thevirtualization layer may include a hypervisor installed in each of thevirtualization servers 403 with the physical computing resources. Knowncloud systems may alternatively be used, e.g., WINDOWS AZURE (MicrosoftCorporation of Redmond Wash.), AMAZON EC2 (Amazon.com Inc. of Seattle,Wash.), IBM BLUE CLOUD (IBM Corporation of Armonk, N.Y.), or others.

Enterprise Mobility Management Architecture

FIG. 5 represents an enterprise mobility technical architecture 500 foruse in a BYOD environment. The architecture enables a user of a mobiledevice 502 to both access enterprise or personal resources from a mobiledevice 502 and use the mobile device 502 for personal use. The user mayaccess such enterprise resources 504 or enterprise services 508 using amobile device 502 that is purchased by the user or a mobile device 502that is provided by the enterprise to user. The user may utilize themobile device 502 for business use only or for business and personaluse. The mobile device may run an iOS operating system, and Androidoperating system, or the like. The enterprise may choose to implementpolicies to manage the mobile device 504. The policies may be implantedthrough a firewall or gateway in such a way that the mobile device maybe identified, secured or security verified, and provided selective orfull access to the enterprise resources. The policies may be mobiledevice management policies, mobile application management policies,mobile data management policies, or some combination of mobile device,application, and data management policies. A mobile device 504 that ismanaged through the application of mobile device management policies maybe referred to as a managed device.

In some embodiments, the operating system of the mobile device may beseparated into a managed partition 510 and an unmanaged partition 512.The managed partition 510 may have policies applied to it to secure theapplications running on and data stored in the managed partition. Theapplications running on the managed partition may be secureapplications. In other embodiments, all applications may execute inaccordance with a set of one or more policy files received separate fromthe application, and which define one or more security parameters,features, resource restrictions, and/or other access controls that areenforced by the mobile device management system when that application isexecuting on the device. By operating in accordance with theirrespective policy file(s), each application may be allowed or restrictedfrom communications with one or more other applications and/orresources, thereby creating a virtual partition. Thus, as used herein, apartition may refer to a physically partitioned portion of memory(physical partition), a logically partitioned portion of memory (logicalpartition), and/or a virtual partition created as a result ofenforcement of one or more policies and/or policy files across multipleapps as described herein (virtual partition). Stated differently, byenforcing policies on managed apps, those apps may be restricted to onlybe able to communicate with other managed apps and trusted enterpriseresources, thereby creating a virtual partition that is impenetrable byunmanaged apps and devices.

The secure applications may be email applications, web browsingapplications, software-as-a-service (SaaS) access applications, WindowsApplication access applications, and the like. The secure applicationsmay be secure native applications 514, secure remote applications 522executed by a secure application launcher 518, virtualizationapplications 526 executed by a secure application launcher 518, and thelike. The secure native applications 514 may be wrapped by a secureapplication wrapper 520. The secure application wrapper 520 may includeintegrated policies that are executed on the mobile device 502 when thesecure native application is executed on the device. The secureapplication wrapper 520 may include meta-data that points the securenative application 514 running on the mobile device 502 to the resourceshosted at the enterprise that the secure native application 514 mayrequire to complete the task requested upon execution of the securenative application 514. The secure remote applications 522 executed by asecure application launcher 518 may be executed within the secureapplication launcher application 518. The virtualization applications526 executed by a secure application launcher 518 may utilize resourceson the mobile device 502, at the enterprise resources 504, and the like.The resources used on the mobile device 502 by the virtualizationapplications 526 executed by a secure application launcher 518 mayinclude user interaction resources, processing resources, and the like.The user interaction resources may be used to collect and transmitkeyboard input, mouse input, camera input, tactile input, audio input,visual input, gesture input, and the like. The processing resources maybe used to present a user interface, process data received from theenterprise resources 504, and the like. The resources used at theenterprise resources 504 by the virtualization applications 526 executedby a secure application launcher 518 may include user interfacegeneration resources, processing resources, and the like. The userinterface generation resources may be used to assemble a user interface,modify a user interface, refresh a user interface, and the like. Theprocessing resources may be used to create information, readinformation, update information, delete information, and the like. Forexample, the virtualization application may record user interactionsassociated with a GUI and communicate them to a server application wherethe server application will use the user interaction data as an input tothe application operating on the server. In this arrangement, anenterprise may elect to maintain the application on the server side aswell as data, files, etc. associated with the application. While anenterprise may elect to “mobilize” some applications in accordance withthe principles herein by securing them for deployment on the mobiledevice, this arrangement may also be elected for certain applications.For example, while some applications may be secured for use on themobile device, others might not be prepared or appropriate fordeployment on the mobile device so the enterprise may elect to providethe mobile user access to the unprepared applications throughvirtualization techniques. As another example, the enterprise may havelarge complex applications with large and complex data sets (e.g.,material resource planning applications) where it would be verydifficult, or otherwise undesirable, to customize the application forthe mobile device so the enterprise may elect to provide access to theapplication through virtualization techniques. As yet another example,the enterprise may have an application that maintains highly secureddata (e.g. human resources data, customer data, engineering data) thatmay be deemed by the enterprise as too sensitive for even the securedmobile environment so the enterprise may elect to use virtualizationtechniques to permit mobile access to such applications and data. Anenterprise may elect to provide both fully secured and fully functionalapplications on the mobile device as well as a virtualizationapplication to allow access to applications that are deemed moreproperly operated on the server side. In an embodiment, thevirtualization application may store some data, files, etc. on themobile phone in one of the secure storage locations. An enterprise, forexample, may elect to allow certain information to be stored on thephone while not permitting other information.

In connection with the virtualization application, as described herein,the mobile device may have a virtualization application that is designedto present GUI's and then record/pass-through user interactions with theGUI. The application may communicate the user interactions to the serverside to be used by the server side application as user interactions withthe application. In response, the application on the server side maytransmit back to the mobile device a new GUI. For example, the new GUImay be a static page, a dynamic page, an animation, or the like, therebyproviding access to remotely located resources.

The secure applications may access data stored in a secure datacontainer 528 in the managed partition 510 of the mobile device. Thedata secured in the secure data container may be accessed by the securewrapped applications 514, applications executed by a secure applicationlauncher 522, virtualization applications 526 executed by a secureapplication launcher 522, and the like. The data stored in the securedata container 528 may include files, databases, and the like. The datastored in the secure data container 528 may include data restricted to aspecific secure application 530, shared among secure applications 532,and the like. Data restricted to a secure application may include securegeneral data 534 and highly secure data 538. Secure general data may usea strong form of encryption such as AES 128-bit encryption or the like,while highly secure data 538 may use a very strong form of encryptionsuch as AES 254-bit encryption. Data stored in the secure data container528 may be deleted from the device upon receipt of a command from thedevice manager 524. The secure applications may have a dual-mode option540. The dual mode option 540 may present the user with an option tooperate the secured application in an unsecured mode. In an unsecuredmode, the secure applications may access data stored in an unsecureddata container 542 on the unmanaged partition 512 of the mobile device502. The data stored in an unsecured data container may be personal data544. The data stored in an unsecured data container 542 may also beaccessed by unsecured applications 548 that are running on the unmanagedpartition 512 of the mobile device 502. The data stored in an unsecureddata container 542 may remain on the mobile device 502 when the datastored in the secure data container 528 is deleted from the mobiledevice 502. An enterprise may want to delete from the mobile deviceselected or all data, files, and/or applications owned, licensed orcontrolled by the enterprise (enterprise data) while leaving orotherwise preserving personal data, files, and/or applications owned,licensed or controlled by the user (personal data). This operation maybe referred to as a selective wipe. With the enterprise and personaldata arranged in accordance to the aspects described herein, anenterprise may perform a selective wipe.

The mobile device may connect to enterprise resources 504 and enterpriseservices 508 at an enterprise, to the public Internet 548, and the like.The mobile device may connect to enterprise resources 504 and enterpriseservices 508 through virtual private network connections. The virtualprivate network connections, also referred to as microVPN orapplication-specific VPN, may be specific to particular applications550, particular devices, particular secured areas on the mobile device,and the like 552. For example, each of the wrapped applications in thesecured area of the phone may access enterprise resources through anapplication specific VPN such that access to the VPN would be grantedbased on attributes associated with the application, possibly inconjunction with user or device attribute information. The virtualprivate network connections may carry Microsoft Exchange traffic,Microsoft Active Directory traffic, HTTP traffic, HTTPS traffic,application management traffic, and the like. The virtual privatenetwork connections may support and enable single-sign-on authenticationprocesses 554. The single-sign-on processes may allow a user to providea single set of authentication credentials, which are then verified byan authentication service 558. The authentication service 558 may thengrant to the user access to multiple enterprise resources 504, withoutrequiring the user to provide authentication credentials to eachindividual enterprise resource 504.

The virtual private network connections may be established and managedby an access gateway 560. The access gateway 560 may include performanceenhancement features that manage, accelerate, and improve the deliveryof enterprise resources 504 to the mobile device 502. The access gatewaymay also re-route traffic from the mobile device 502 to the publicInternet 548, enabling the mobile device 502 to access publiclyavailable and unsecured applications that run on the public Internet548. The mobile device may connect to the access gateway via a transportnetwork 562. The transport network 562 may be a wired network, wirelessnetwork, cloud network, local area network, metropolitan area network,wide area network, public network, private network, and the like.

The enterprise resources 504 may include email servers, file sharingservers, SaaS applications, Web application servers, Windows applicationservers, and the like. Email servers may include Exchange servers, LotusNotes servers, and the like. File sharing servers may include ShareFileservers, and the like. SaaS applications may include Salesforce, and thelike. Windows application servers may include any application serverthat is built to provide applications that are intended to run on alocal Windows operating system, and the like. The enterprise resources504 may be premise-based resources, cloud based resources, and the like.The enterprise resources 504 may be accessed by the mobile device 502directly or through the access gateway 560. The enterprise resources 504may be accessed by the mobile device 502 via a transport network 562.The transport network 562 may be a wired network, wireless network,cloud network, local area network, metropolitan area network, wide areanetwork, public network, private network, and the like.

The enterprise services 508 may include authentication services 558,threat detection services 564, device manager services 524, file sharingservices 568, policy manager services 570, social integration services572, application controller services 574, and the like. Authenticationservices 558 may include user authentication services, deviceauthentication services, application authentication services, dataauthentication services and the like. Authentication services 558 mayuse certificates. The certificates may be stored on the mobile device502, by the enterprise resources 504, and the like. The certificatesstored on the mobile device 502 may be stored in an encrypted locationon the mobile device, the certificate may be temporarily stored on themobile device 502 for use at the time of authentication, and the like.Threat detection services 564 may include intrusion detection services,unauthorized access attempt detection services, and the like.Unauthorized access attempt detection services may include unauthorizedattempts to access devices, applications, data, and the like. Devicemanagement services 524 may include configuration, provisioning,security, support, monitoring, reporting, and decommissioning services.File sharing services 568 may include file management services, filestorage services, file collaboration services, and the like. Policymanager services 570 may include device policy manager services,application policy manager services, data policy manager services, andthe like. Social integration services 572 may include contactintegration services, collaboration services, integration with socialnetworks such as Facebook, Twitter, and LinkedIn, and the like.Application controller services 574 may include management services,provisioning services, deployment services, assignment services,revocation services, wrapping services, and the like.

The enterprise mobility technical architecture 500 may include anapplication store 578. The application store 578 may include unwrappedapplications 580, pre-wrapped applications 582, and the like.Applications may be populated in the application store 578 from theapplication controller 574. The application store 578 may be accessed bythe mobile device 502 through the access gateway 560, through the publicInternet 548, or the like. The application store may be provided with anintuitive and easy to use User Interface. The application store 578 mayprovide access to a software development kit 584. The softwaredevelopment kit 584 may provide a user the capability to secureapplications selected by the user by wrapping the application asdescribed previously in this description. An application that has beenwrapped using the software development kit 584 may then be madeavailable to the mobile device 502 by populating it in the applicationstore 578 using the application controller 574.

The enterprise mobility technical architecture 500 may include amanagement and analytics capability 588. The management and analyticscapability 588 may provide information related to how resources areused, how often resources are used, and the like. Resources may includedevices, applications, data, and the like. How resources are used mayinclude which devices download which applications, which applicationsaccess which data, and the like. How often resources are used mayinclude how often an application has been downloaded, how many times aspecific set of data has been accessed by an application, and the like.

FIG. 6 is another illustrative enterprise mobility management system600. Some of the components of the mobility management system 500described above with reference to FIG. 5 have been omitted for the sakeof simplicity. The architecture of the system 600 depicted in FIG. 6 issimilar in many respects to the architecture of the system 500 describedabove with reference to FIG. 5 and may include additional features notmentioned above.

In this case, the left hand side represents a managed mobile device 602with a client agent 604, which interacts with gateway server 606 (whichincludes Access Gateway and App Controller functionality) to accessvarious enterprise resources 608 and services 609 such as Exchange,Sharepoint, PKI Resources, Kerberos Resources, Certificate Issuanceservice, as shown on the right hand side above. Although notspecifically shown, the mobile device 602 may also interact with anenterprise application store (StoreFront) for the selection anddownloading of applications.

The client agent 604 acts as the UI (user interface) intermediary forWindows apps/desktops hosted in an Enterprise data center, which areaccessed using the HDX/ICA display remoting protocol. The client agent604 also supports the installation and management of native applicationson the mobile device 602, such as native iOS or Android applications.For example, the managed applications 610 (mail, browser, wrappedapplication) shown in the figure above are all native applications thatexecute locally on the device. Client agent 604 and applicationmanagement framework of this architecture act to provide policy drivenmanagement capabilities and features such as connectivity and SSO(single sign on) to enterprise resources/services 608. The client agent604 handles primary user authentication to the enterprise, normally toAccess Gateway (AG) with SSO to other gateway server components. Theclient agent 604 obtains policies from gateway server 606 to control thebehavior of the managed applications 610 on the mobile device 602.

The Secure IPC links 612 between the native applications 610 and clientagent 604 represent a management channel, which allows client agent tosupply policies to be enforced by the application management framework614 “wrapping” each application. The IPC channel 612 also allows clientagent 604 to supply credential and authentication information thatenables connectivity and SSO to enterprise resources 608. Finally theIPC channel 612 allows the application management framework 614 toinvoke user interface functions implemented by client agent 604, such asonline and offline authentication.

Communications between the client agent 604 and gateway server 606 areessentially an extension of the management channel from the applicationmanagement framework 614 wrapping each native managed application 610.The application management framework 614 requests policy informationfrom client agent 604, which in turn requests it from gateway server606. The application management framework 614 requests authentication,and client agent 604 logs into the gateway services part of gatewayserver 606 (also known as NetScaler Access Gateway). Client agent 604may also call supporting services on gateway server 606, which mayproduce input material to derive encryption keys for the local datavaults 616, or provide client certificates which may enable directauthentication to PKI protected resources, as more fully explainedbelow.

In more detail, the application management framework 614 “wraps” eachmanaged application 610. This may be incorporated via an explicit buildstep, or via a post-build processing step. The application managementframework 614 may “pair” with client agent 604 on first launch of anapplication 610 to initialize the Secure IPC channel and obtain thepolicy for that application. The application management framework 614may enforce relevant portions of the policy that apply locally, such asthe client agent login dependencies and some of the containment policiesthat restrict how local OS services may be used, or how they mayinteract with the application 610.

The application management framework 614 may use services provided byclient agent 604 over the Secure IPC channel 612 to facilitateauthentication and internal network access. Key management for theprivate and shared data vaults 616 (containers) may be also managed byappropriate interactions between the managed applications 610 and clientagent 604. Vaults 616 may be available only after online authentication,or may be made available after offline authentication if allowed bypolicy. First use of vaults 616 may require online authentication, andoffline access may be limited to at most the policy refresh periodbefore online authentication is again required.

Network access to internal resources may occur directly from individualmanaged applications 610 through Access Gateway 606. The applicationmanagement framework 614 is responsible for orchestrating the networkaccess on behalf of each application 610. Client agent 604 mayfacilitate these network connections by providing suitable time limitedsecondary credentials obtained following online authentication. Multiplemodes of network connection may be used, such as reverse web proxyconnections and end-to-end VPN-style tunnels 618.

The Mail and Browser managed applications 610 have special status andmay make use of facilities that might not be generally available toarbitrary wrapped applications. For example, the Mail application mayuse a special background network access mechanism that allows it toaccess Exchange over an extended period of time without requiring a fullAG logon. The Browser application may use multiple private data vaultsto segregate different kinds of data.

This architecture supports the incorporation of various other securityfeatures. For example, gateway server 606 (including its gatewayservices) in some cases will not need to validate AD passwords. It canbe left to the discretion of an enterprise whether an AD password isused as an authentication factor for some users in some situations.Different authentication methods may be used if a user is online oroffline (i.e., connected or not connected to a network).

Step up authentication is a feature wherein gateway server 606 mayidentify managed native applications 610 that are allowed to have accessto highly classified data requiring strong authentication, and ensurethat access to these applications is only permitted after performingappropriate authentication, even if this means a re-authentication isrequired by the user after a prior weaker level of login.

Another security feature of this solution is the encryption of the datavaults 616 (containers) on the mobile device 602. The vaults 616 may beencrypted so that all on-device data including files, databases, andconfigurations are protected. For on-line vaults, the keys may be storedon the server (gateway server 606), and for off-line vaults, a localcopy of the keys may be protected by a user password. When data isstored locally on the device 602 in the secure container 616, it ispreferred that a minimum of AES 256 encryption algorithm be utilized.

Other secure container features may also be implemented. For example, alogging feature may be included, wherein all security events happeninginside an application 610 are logged and reported to the backend. Datawiping may be supported, such as if the application 610 detectstampering, associated encryption keys may be written over with randomdata, leaving no hint on the file system that user data was destroyed.Screenshot protection is another feature, where an application mayprevent any data from being stored in screenshots. For example, the keywindow's hidden property may be set to YES. This may cause whatevercontent is currently displayed on the screen to be hidden, resulting ina blank screenshot where any content would normally reside.

Local data transfer may be prevented, such as by preventing any datafrom being locally transferred outside the application container, e.g.,by copying it or sending it to an external application. A keyboard cachefeature may operate to disable the autocorrect functionality forsensitive text fields. SSL certificate validation may be operable so theapplication specifically validates the server SSL certificate instead ofit being stored in the keychain. An encryption key generation featuremay be used such that the key used to encrypt data on the device isgenerated using a passphrase supplied by the user (if offline access isrequired). It may be XORed with another key randomly generated andstored on the server side if offline access is not required. KeyDerivation functions may operate such that keys generated from the userpassword use KDFs (key derivation functions, notably PBKDF2) rather thancreating a cryptographic hash of it. The latter makes a key susceptibleto brute force or dictionary attacks.

Further, one or more initialization vectors may be used in encryptionmethods. An initialization vector will cause multiple copies of the sameencrypted data to yield different cipher text output, preventing bothreplay and cryptanalytic attacks. This will also prevent an attackerfrom decrypting any data even with a stolen encryption key if thespecific initialization vector used to encrypt the data is not known.Further, authentication then decryption may be used, wherein applicationdata is decrypted only after the user has authenticated within theapplication. Another feature may relate to sensitive data in memory,which may be kept in memory (and not in disk) only when it's needed. Forexample, login credentials may be wiped from memory after login, andencryption keys and other data inside objective-C instance variables arenot stored, as they may be easily referenced. Instead, memory may bemanually allocated for these.

An inactivity timeout may be implemented, wherein after a policy-definedperiod of inactivity, a user session is terminated.

Data leakage from the application management framework 614 may beprevented in other ways. For example, when an application 610 is put inthe background, the memory may be cleared after a predetermined(configurable) time period. When backgrounded, a snapshot may be takenof the last displayed screen of the application to fasten theforegrounding process. The screenshot may contain confidential data andhence should be cleared.

Another security feature relates to the use of an OTP (one timepassword) 620 without the use of an AD (active directory) 622 passwordfor access to one or more applications. In some cases, some users do notknow (or are not permitted to know) their AD password, so these usersmay authenticate using an OTP 620 such as by using a hardware OTP systemlike SecurID (OTPs may be provided by different vendors also, such asEntrust or Gemalto). In some cases, after a user authenticates with auser ID, a text is sent to the user with an OTP 620. In some cases, thismay be implemented only for online use, with a prompt being a singlefield.

An offline password may be implemented for offline authentication forthose applications 610 for which offline use is permitted via enterprisepolicy. For example, an enterprise may want StoreFront to be accessed inthis manner. In this case, the client agent 604 may require the user toset a custom offline password and the AD password is not used. Gatewayserver 606 may provide policies to control and enforce passwordstandards with respect to the minimum length, character classcomposition, and age of passwords, such as described by the standardWindows Server password complexity requirements, although theserequirements may be modified.

Another feature relates to the enablement of a client side certificatefor certain applications 610 as secondary credentials (for the purposeof accessing PKI protected web resources via the application managementframework micro VPN feature). For example, an application such as@WorkMail may utilize such a certificate. In this case,certificate-based authentication using ActiveSync protocol may besupported, wherein a certificate from the client agent 604 may beretrieved by gateway server 606 and used in a keychain. Each managedapplication may have one associated client certificate, identified by alabel that is defined in gateway server 606.

Gateway server 606 may interact with an Enterprise special purpose webservice to support the issuance of client certificates to allow relevantmanaged applications to authenticate to internal PKI protectedresources.

The client agent 604 and the application management framework 614 may beenhanced to support obtaining and using client certificates forauthentication to internal PKI protected network resources. More thanone certificate may be supported, such as to match various levels ofsecurity and/or separation requirements. The certificates may be used bythe Mail and Browser managed applications, and ultimately by arbitrarywrapped applications (provided those applications use web service stylecommunication patterns where it is reasonable for the applicationmanagement framework to mediate https requests).

Application management client certificate support on iOS may rely onimporting a PKCS 12 BLOB (Binary Large Object) into the iOS keychain ineach managed application for each period of use. Application managementframework client certificate support may use a HTTPS implementation withprivate in-memory key storage. The client certificate will never bepresent in the iOS keychain and will not be persisted except potentiallyin “online-only” data value that is strongly protected.

Mutual SSL may also be implemented to provide additional security byrequiring that a mobile device 602 is authenticated to the enterprise,and vice versa. Virtual smart cards for authentication to gateway server606 may also be implemented.

Both limited and full Kerberos support may be additional features. Thefull support feature relates to an ability to do full Kerberos login toAD 622, using an AD password or trusted client certificate, and obtainKerberos service tickets to respond to HTTP Negotiate authenticationchallenges. The limited support feature relates to constraineddelegation in AFEE, where AFEE supports invoking Kerberos protocoltransition so it can obtain and use Kerberos service tickets (subject toconstrained delegation) in response to HTTP Negotiate authenticationchallenges. This mechanism works in reverse web proxy (aka CVPN) mode,and when http (but not https) connections are proxied in VPN andMicroVPN mode.

Another feature relates to application container locking and wiping,which may automatically occur upon jail-break or rooting detections, andoccur as a pushed command from administration console, and may include aremote wipe functionality even when an application 610 is not running.

A multi-site architecture or configuration of StoreFront and AppController may be supported that allows users to be service from one ofseveral different locations in case of failure.

In some cases, managed applications 610 may be allowed to access acertificate and private key via an API (example OpenSSL). Trustedmanaged applications 610 of an enterprise may be allowed to performspecific Public Key operations with an application's client certificateand private key. Various use cases may be identified and treatedaccordingly, such as when an application behaves like a browser and nocertificate access is required, when an application reads a certificatefor “who am I,” when an application uses the certificate to build asecure session token, and when an application uses private keys fordigital signing of important data (e.g. transaction log) or fortemporary data encryption.

Illustrative Embodiment(S)

FIG. 7 illustrates a sample interface of a mobile device, and FIGS. 8-14illustrate sample embodiments of methods for determining an operationmode for an application. The methods depicted in FIGS. 8-14 may becombined in any suitable manner in various embodiments. The sampleinterface depictured in FIG. 7 may be displayed on a mobile device, suchas device 107, 109, 240, 502, and/or 602, and the methods depicted inFIGS. 8-14 may be implemented by such a mobile device.

In FIG. 8, a flowchart of example method steps for determining anapplication mode for an application is shown. The method of FIG. 8 maybegin at step 802, where a plurality of applications are presented. Forexample, a plurality of applications may be presented to a user on amobile device. FIG. 7 illustrates an embodiment where user interface 700displayed on a mobile device (e.g., tablet, smart phone, or the like)presents Applications A 700, B 701, C 702, and E 703 to a user. This ismerely an example, and the plurality of applications may be presented inany suitable manner. In an embodiment, the plurality of applications maycomprise email applications, web browsing applications,software-as-a-service (SaaS) access applications, and the like.

The method of FIG. 8 may proceed from step 802 to step 804, where aselection for one of the plurality of applications is received. Withreference to an embodiment depicted in FIG. 7, a user of a mobile devicemay select one of the presented applications by, for example, pressing adisplay of the mobile device to select the application. This is merelyan example, and the application may be selected in any suitable manner.

The method of FIG. 8 may proceed from step 804 to step 806, where acontext for the selected applications is determined based on one or moreoperational parameters of the device executing the selected application.For example, a context may be based on an account to be accessed by theapplication, a location of the mobile device or a network connectivitystatus of the mobile device executing the application, or based on anyother operational parameter. The methods of FIGS. 9-13, furtherdescribed below, illustrate various embodiments where example contextsare described.

The method of FIG. 8 may proceed from step 804 to step 806, where anoperation mode for the selected application is determined based on thecontext. In an embodiment, the operations modes may comprise managed andunmanaged modes, e.g., representing work and non-work modes of a devicefor when a user is performing employment-related versus personalactivities, respectively. The work mode may provide access to enterpriseresources and include one or more content filters and/or restrictions,whereas the non-work mode might apply policies (or no policies) and/orcontent filters/restrictions (or none) that allow access to onlynon-enterprise related resources.

In addition, there may be multiple different managed modes, e.g., basedon different security levels of various users or sets of credentialsprovided by a user, different user roles identified by a set ofcredentials (e.g., manager versus staff employees), geographic locationsfrom which the device is operated, network locations, operationalenvironment (e.g., a healthcare-related managed mode versus a financialindustry managed mode), or based on any other contextual determination.Some modes may be based on multiple contexts, e.g., location and role.In one such combination a first managed mode may provide applicablepolicies for a healthcare provider, whereas a second managed mode mayapply applicable policies for a patient. As a device is passed betweenthe two users, the user (or software based on user action) may initiatea change of mode as the device is passed to a user having a differentrole. The new user may be required to enter appropriate credentials tochange modes, e.g., when changing to a more secure mode. The healthcareprovider mode may provide access to a wide array of patient records,resources, scheduling details, financial records, and other information,whereas a patient mode may be limited to only that patient'sinformation, e.g., based on HIPPA and other privacy considerations.Other combinations of contextual decisions may also be used.

In an embodiment, the determined context may be compared to a storedpolicy in order to determine an operation mode. A mobile device, such asmobile device 502, may store one or more policies used to determine anoperation mode for an application. In an embodiment, the policies may bestored remotely, such as at policy manager 570, described above withreference to FIG. 5, or may be stored locally on the device. In anexample, a context may comprise a selected application configured toaccess a secure account, such as an email application configured toaccess a secure email account. This context may be compared to a storedpolicy. For instance, the stored policy may define that an emailapplication that is configured to access a secure email account is to berun as a managed application. The stored policy may further indicatethat the email application, when configured to access a personal accountof the device user, may operate in an unmanaged mode. Additionalcontexts and policies will be described with respect to FIGS. 9-13.

The method of FIG. 8 may proceed from step 806 to step 808, where theselected application is run in the determined operation mode. Forexample, the operation mode may be determined as unmanaged, or as one ofmultiple managed modes, and the selected application may be run in thedetermined mode.

In an embodiment, a managed operation mode may include running theapplication as a part of the managed partition 510 of mobile device 502,as described above with reference to FIG. 5. As such, the managedapplication may be run as secure native applications 514, secure remoteapplications 522 executed by a secure application launcher 518,virtualization applications 526 executed by a secure applicationlauncher 518, and the like.

In an embodiment, an application running in managed mode may access datastored in a secure data container 528 in the managed partition 510(physical, logical, or virtual) of the mobile device. The data stored inthe secure data container 528 may include data restricted to a specificsecure/managed application 530, shared among other secure/managedapplications, and the like. Data restricted to a secure application mayinclude secure general data 534 and highly secure data 538. Differentlevels and types of security features may be used to differentiatelevels of secure data. In an embodiment, an application running inmanaged mode may save, modify, or delete data in secure data container528. The data saved or modified may be encrypted similar to other datastored in secure data container 528.

In an embodiment, an application running in managed mode may connect toenterprise resources 504 and enterprise services 508 through virtualprivate network connections, as described about with reference to FIG.5. The virtual private network connections may be microVPNs, which arespecific to a particular application, such as the selected application,particular devices, particular secured areas on the mobile device, andthe like. For example, wrapped applications in a secured area of thephone may access enterprise resources through an application specificVPN such that access to the VPN would be granted based on attributesassociated with the application, possibly in conjunction with user ordevice attribute information, and policy information.

In an embodiment, an application running in managed mode may encryptdata transmitted from the application. For example, an applicationrunning in managed mode may be communicating with a computing deviceover a network, and the data transmitted from the application to thedevice may be encrypted. In addition, the data communicated from thecomputing device to the application may also be encrypted, and theapplication running in managed mode may be configured to decrypt thereceived data.

In an embodiment, an application running in managed mode my access asecure portal. For example, an application may connect to a computingdevice over a network, for example, a microVPN, and may access a secureportal that might not be access by unsecured applications, such asapplications running in unmanaged mode.

In an embodiment, an unmanaged operation mode may include running theapplication as a part of the unmanaged partition 512 (physical, logical,or virtual) of mobile device 502, as described above with reference toFIG. 5. In an unmanaged mode, the application may access data stored inan unsecured data container 542 on the unmanaged partition 512 of themobile device 502. The data stored in an unsecured data container may bepersonal data 544.

In an embodiment, where more than one managed mode is possible, anapplication running in a less secure managed mode may be run similar toan application running in the more secure managed mode, but might notinclude all aspects of the latter. For example, an application runningin the less secure managed mode may have the information transmittedfrom the application over a network encrypted, but the application mightnot have access to secure data container 528, as described withreference to FIG. 5. In another example, an application running in theless secure managed mode may have access to secure data container 528,but might not be able to connect to enterprise resources 504 andenterprise services 508 through virtual private network connections.Accordingly, depending on the determined context, an application runningin a less secure managed mode may include aspects of an applicationrunning in the more secure managed mode and aspects of an applicationrunning in unmanaged mode.

In FIGS. 9-13, flowcharts of example method steps for determining acontext and operation mode for an application are shown. In anembodiment, steps 806 and 808 of FIG. 8 may comprise the method steps ofany one or more of FIGS. 9-13. The method of FIG. 9 may begin at step902, where an account to be accessed by a selected application isdetected. For example, a selected application may comprise an emailapplication and an email account that the email application isconfigured to access may be detected. In this example, the emailapplication may be able to access multiple email accounts, such as anenterprise email account and a personal email account, and the accountthat the email application is configured to access at the time ofrunning may be determined as the context account to be accessed.

The method of FIG. 9 may proceed from step 902 to step 904, where anaccount type of the account to be accessed may be determined. Theaccount type may comprise a context for the selected application. Forexample, a selected application may comprise an email application andthe email application may be configured to access an enterprise account.In another example, the email application may be configured to access apersonal account.

The method of FIG. 9 may proceed from step 904 to step 906, where anaccount type may be compared with an account type policy. For example, apolicy may define that an email application that is to access anenterprise account should run in managed mode and an email applicationthat is to access a personal account should run in unmanaged mode. Themethod of FIG. 9 may proceed from step 906 to step 908, where anoperation mode is determined based on the comparison.

The method of FIG. 10 may begin at step 1002, where a location for amobile device is determined. For example, a mobile device, such asmobile device 502, may implement the method of FIG. 10, and a locationfor the mobile device may be determined. The location may be determinedby GPS, signal triangulation, or any other suitable or otherwise knownmanner. The location may comprise a context for the selectedapplication.

The method of FIG. 10 may proceed from step 1002 to step 1004, where adetermined location may be compared with a location policy. For example,a policy may define that a selected application run in a more securemanaged mode when in a certain location, for example, on companypremises. In an embodiment, a policy may define that a selectedapplication run in a less secure managed mode when in a certainlocation, for example, when the determined location is inside the UnitedStates but off company premises. For example, the less secure managedmode may encrypt communication to and from the selected application, butmight not allow access to enterprise resources, such as resources 504.In another embodiment, a policy may define that a selected applicationrun in unmanaged mode when in a certain location, for example, when thedetermined location is outside the United States. The method of FIG. 10may proceed from step 1004 to step 1006, where an operation mode isdetermined based on the comparison.

Alternatively or in addition to physical location, a network locationmay also or instead be used to determine whether access is permitted.For example, network location may refer to whether a user is eitherinternal to a data center (or pre-approved Wifi access point), or isexternal to it. Appropriate access modes may be based on such adetermination.

The method of FIG. 11 may begin at step 1102, where it is monitoredwhether a predetermined application is running on a device. For example,a mobile device, such as mobile device 502, may implement the method ofFIG. 11, and the mobile device may be monitored to determine whether apredetermined application is running. The predetermined application maycomprise any application capable of running on the mobile device, such aclient agent 604 as described with reference to FIG. 6. The monitoredpredetermined application may comprise a context for the selectedapplication.

The method of FIG. 11 may proceed from step 1102 to step 1104, where amonitored application is compared against a policy. For example, apolicy may define that a selected application run in managed mode when apredetermined application, such as client agent 604, is running and thatthe selected application run in unmanaged mode when the predeterminedapplication is not running. The method of FIG. 11 may proceed from step1104 to step 1106, where an operation mode is determined based on thecomparison.

The method of FIG. 12 may begin at step 1202, one or more networkconnections are detected. For example, a mobile device, such as mobiledevice 502, may implement the method of FIG. 12, and the networkconnections that the mobile device makes may be detected. In an example,network connections may comprise a connection to a cellular network, aconnection to a WIFI network, or a connection to a Wireless Local AreaNetwork (WLAN), or the like. The one or more network connections maycomprise a context for the selected application.

The method of FIG. 12 may proceed from step 1202 to step 1204, wheredetected network connections are compared against a network connectionpolicy. For example, a policy may define that a selected application runin managed mode when a mobile device is connected to an internalnetwork, such as a WLAN internal to a company, and that the selectedapplication run in unmanaged mode when the mobile device is onlyconnected to a wireless network, such as cellular network or WIFInetwork. The method of FIG. 12 may proceed from step 1204 to step 1206,where an operation mode is determined based on the comparison.

The method of FIG. 13 may begin at step 1302, where one or more settingsfor a mobile device are detected. For example, a mobile device, such asmobile device 502, may implement the method of FIG. 13, and one or moresettings for the mobile device may be detected. In an example, it may bedetected whether the mobile device has a lock screen, such as a PINrequired for using the mobile device, or it may be detected whether themobile device is jailbroken/rooted, e.g., has received after-marketmodifications. The one or more settings may comprise a context for theselected application.

The method of FIG. 13 may proceed from step 1302 to step 1304, wheredetected settings are compared against a settings policy. For example, apolicy may define that a selected application might not run in managedmode if the mobile device does not have a lock screen or if the mobiledevice is jailbroken/rooted. The method of FIG. 13 may proceed from step1304 to step 1306, where an operation mode is determined based on thecomparison. In an embodiment, when running the selected application inthe determined mode, an indicator may be displayed on the mobile devicethat informs a user of certain policies, such as a requirement for amobile device to have a lock screen before the mobile device is allowedto run the selected application in managed mode. FIGS. 9-13 describe aplurality of contexts, and any other suitable context and correspondingpolicy may be implemented.

In an embodiment, one or more of the contexts described in FIGS. 9-13may be combined and these contexts may be compared against a policy forthe selected application. For example, contexts for a selectedapplication may comprise an account type to be accessed as an enterpriseemail account and a detected network connection as a cellular network.In this example, the policy may define that when an enterprise accountis attempted to be accessed over a cellular network, the selectedapplication should be run in managed mode. The policy may be defined inthis way because the selected application may encrypt the communicationwith the enterprise email account, and therefore the risk of sendingsecure traffic over a cellular network may be mitigated.

In another example, contexts for a selected application may comprise adetermined location outside of the United States and a networkconnection with a WLAN internal to a company. A policy may define that aselected application is to run in managed mode when a determinedlocation is outside the United States and a network connection is with aWLAN internal to a company. The policy may be defined in this waybecause a network connection with a WLAN internal to a company mitigatesthe risk associated with secure communications outside of the UnitedStates.

In an embodiment, the one or more contexts as described in FIGS. 9-13may include a priority. For example, a context for a selectedapplication may comprise a determination that the mobile device isjailbroken/rooted, and a policy may define that a selected applicationis to run only in unmanaged mode when a context indicates ajailbroken/rooted mobile device, regardless of what other contextsindicate. Accordingly, a jailbroken/rooted mobile device will have aselected application run in unmanaged mode even when the mobile deviceis connected to a WLAN internal to a company or if the selectedapplication is attempting to access an enterprise account.

In an embodiment, a policy may indicate that a selected application isto be run in a less secure managed mode based on a plurality of contextsas described in FIGS. 9-13. For example, contexts for a selectedapplication may comprise an account type to be accessed as an enterpriseemail account and a detected network connection as a cellular network.In this example, the policy may define that when an enterprise accountis attempted to be accessed over a cellular network, the selectedapplication should be run in the less secure managed mode. The lesssecure managed mode may encrypt communication to and from the selectedapplication, but might not allow access to enterprise resources, such asresources 504. The policy may be defined in this way because theencrypted communication with the enterprise email account may be a lowrisk communication, and allowing access to enterprise resources may be ahigh risk communication.

In FIG. 14, a flowchart of example method steps for switching anoperation mode for an application is shown. For example, the methodsteps of FIG. 14 may follow the method steps of FIG. 8. The method ofFIG. 14 may begin at step 1402, where one or more contexts may bemonitored while a selected application is running. In an embodiment, oneor more of the contexts described with reference to FIGS. 9-13 may bemonitored. For example, a mobile device running a selected applicationmay be connected to a cellular network and while the selectedapplication is running, the mobile device may make a new networkconnection with a WLAN internal to a company.

The method of FIG. 14 may proceed from step 1402 to step 1404, where achange in an operation mode for a selected application is detected basedon the monitoring. Stated differently, the mobile device may detect achange in information that formed the basis for selecting a particularoperational mode. For example, a selected application may be running inunmanaged mode, and once a mobile application running the selectedapplication connects to a WLAN internal to a company, a policy maydefine that the operation mode for the selected application shouldswitch to managed mode. The method of FIG. 14 may proceed from step 1404to step 1406, where the operation mode for the selected application isswitched.

In an embodiment, a manager, such as a mobile device manager, may manageone or more mobile devices. In this example, the mobile device may bereferred to as an enrolled device. In an embodiment, a mobile device maybe managed based on software installed on the a managed, such as aclient agent 604 of FIG. 6.

In an example, client agent 604 may further include a connectionmanagement software development kit (SDK), a connection manager 520, aconnection/status application programming interface (API), a set ofvirtualization services, a runtime SDK, a platform SDK, and a clientcore.

The virtualization service in the client agent architecture may include,for example, a graphics service, a desktop integration service, amultimedia service, input/output services, a smart card service, aprinting service, and the like. The runtime SDK may be, for example,Independent Computing Architecture (ICA) runtime SDK, including an ICAengine. The platform SDK may be, for example, an ICA platform SDK orother platform SDK, and may include various subcomponents such as avirtual channel SDK, a configuration and load manager, a tracesubcomponent, a platform abstraction SDK, and the like. The client coremay include, for example, a core protocol for remote access to terminalservices (e.g., a Winstation driver with a core ICA protocol), a reducersubcomponent configured to perform compression and prioritization, amulti-stream ICA, a TCP stack with session reliability, proxy, and SSL,and a UDP subcomponent. The client core also may include implementationsof platform-specific subcomponents, such as graphics smart card andthread support, configuration and load manager libraries, an SSL SDK,and the like.

A mobile device may be enrolled in an enterprise system using, forexample, client agent 604. For example, in an enrolled client device602, a client agent 604 may interact with a gateway server 606 or otheraccess gateway to access various enterprise resources 608 and services609. Enrolling a device may involve bring your own device (BYOD) andrelated technologies, and opting in to an MDM or similar system.Enrollment of a device with a company account (or other organizationaccount) may involve pushing certificates to the device and registeringthe device with a device management server of an enterprise system.After enrollment, the device may be “governed” by a companyadministrator (or other organization administrator) using mobile devicemanagement (MDM) and/or mobile device experience technology (Applicationmanagement framework) policies that are pushed to the device. Enrolleddevices may also be referred to as managed devices. Stated differently,after enrollment, a device may become a managed device as describedherein. In certain examples, to enroll a device in an enterprise system,a client agent 604 and/or an application enrollment token may bedownloaded and installed on the device. The application enrollment tokenmay be derived from a certificate of a company or other organization towhich the device will be enrolled. After downloading the client agent604 and application enrollment token, the device user may be prompted toopen the token and add the company account (or other organizationaccount) to the device.

In an embodiment, an enrolled mobile device, such as mobile device 502of FIG. 5, may be managed by a service, such as device manager 524 ofFIG. 5. Device manager 524 may provide services that includeconfiguration, provisioning, security, support, monitoring, reporting,and decommissioning. For example, device manager 524 may monitor whatapplications are installed on an enrolled/managed mobile device. In thisexample, device manager 524 may store/access a list of black-listedapplications and may further determine the installation of ablack-listed application on an enrolled/managed mobile device. Ablack-listed application may comprise an application that is suspectedmalware or any other suitable application. In another example, devicemanager 524 may monitor an operating state for an enrolled mobiledevice. In this example, device manager 524 may determine that anenrolled mobile device has been jailbroken/rooted. Device manager 524may perform various management activities on an enrolled device based onthese determinations.

In another example, device manager 524 may monitor a network connectionfor the mobile device. In this example, device manager 524 may determinethat an enrolled mobile device is connected to a cellular network, awireless local area network (WLAN), a local area network (LAN), acombination of these, or any other suitable network. In another example,device manager 524 may monitor a location for the mobile device. In thisexample, device manager 524 may determine the geographic location forthe mobile device, such as the latitude and longitude, the country, thestate, any suitable region, or any other suitable location for themobile device.

In another example, device manager 524 may monitor whether a particularapplication is running on the mobile device. In this example, devicemanager 524 may determine whether the particular application, such asclient agent 604 of FIG. 6, is running on the mobile device. Devicemanager 524 may perform various management activities on an enrolleddevice based on these determinations.

In an embodiment, an application installed on an enrolled mobile devicemay run in managed mode or unmanaged mode, as described above. In anembodiment, a managed operation mode may include running the applicationas a part of the managed partition 510 of mobile device 502, asdescribed above with reference to FIG. 5. In an embodiment, anapplication running in managed mode may access data stored in a securedata container 528 in the managed partition 510 of the mobile device.The data stored in the secure data container 528 may include datarestricted to a specific secure application 530, shared among othersecure applications, and the like. Data restricted to a secureapplication may include secure general data 534 and highly secure data538. Secure general data may use a strong form of encryption such as AES128-bit encryption or the like, while highly secure data 538 may use avery strong form of encryption such as AES 254-bit encryption. Othertypes of encryption may be used, and other levels and types of securitymeasures may be applied based on a desired level and/or type ofsecurity, as well as different key recovery features. In an embodiment,an application running in managed mode may save, modify, or delete datain secure data container 528. The data saved or modified may beencrypted similar to other data stored in secure data container 528.

In an embodiment, a managed mode may comprise an enterprise mode and anunmanaged mode may comprise a personal mode. For example, when theapplication is running in managed mode, or enterprise mode, theapplication may have access to resources stored on a secure server(e.g., enterprise data). A device manager 524 managing the device may beassociated with an enterprise. In this example, the application runningin managed mode may be able to communicate with one or more servers(e.g., gateway server 606) that grant the application access toenterprise data. When the application is running in unmanaged mode, orpersonal mode, the application may not have access to the enterprisedata.

In an embodiment, an application that is capable of running in managedmode or unmanaged mode may leverage storage policies for storing dataassociated with the application. In FIG. 15, a flowchart of examplemethod steps for managing an application that runs in multiple modes isshown. FIG. 15 may begin at step 1502, where an application runs on amobile device in one of managed mode or unmanaged mode. For example, anapplication capable of running in managed mode or unmanaged mode, asdescribed above, may run in one of these modes.

The process of FIG. 15 may proceed from step 1502 to step 1504, where arequest is received to store data associated with the application. Forexample, when the application is running in managed mode, a request maybe received to store data, such as secured data accessed from a securedserver (e.g., gateway server 606). In such an example, the secured datamay comprise enterprise data, as described above. In another example,when the application is running in unmanaged mode, a request may bereceived to store data, such as personal data.

The process of FIG. 15 may proceed from step 1504 to step 1506, wheredata is stored on the mobile device according to a storage protocol. Astorage protocol may define the manner in which the requested data is tobe stored on the mobile device. For example, when the application isrunning in managed mode, the data may be stored according to a firstprotocol, and when the application is running in unmanaged mode, thedata may be stored according to a second protocol.

In an embodiment, the first storage protocol may define that therequested data may be stored in a first data container, such as asecured data container (e.g., secured data container 528). In thisexample, the data stored in the first data container may not beaccessible to the application while the application is running inunmanaged mode. In an embodiment, the second storage protocol may definethat the requested data may be stored in a second data containerdifferent from the first data container. The second data container maycomprise a general data container that stores, for example, personaldata.

In an embodiment, the first storage protocol may define that therequested data may be encrypted prior to storage. In this example, thedata may be encrypted using a first key and, in some embodiments, thefirst key may be associated with a device manager that manages thedevice (e.g., device manager 524). In an embodiment, the second storageprotocol may define that the requested data may be encrypted prior tostorage using a second key different from the first key. In anotherexample, the first storage protocol may define that the requested datamay be stored unencrypted.

Stored data may be automatically updated when a storage protocol changesor is modified. For example, a policy may be updated that changes theencryption scheme used for data storage from a first type of encryptionto a second type of encryption. When this occurs, the mobile device mayautomatically decrypt the stored data based on the first type ofencryption and re-encrypt the stored data based on the second type ofencryption using the new or revised policy. In this manner stored datamay always be kept compliant with a current storage policy.

In an embodiment, the first storage protocol may define that therequested data may be stored in association with a managed account. Theapplication running in managed mode may be associated with a managedaccount. For example, a cloud storage application that, while running inmanaged mode, allows access to secured data may be associated with amanaged account used to gain access to the secured data. The requesteddata may be stored in association with this managed account. In anembodiment, the first storage protocol may define that the requesteddata stored may be managed by device manager 524.

Accordingly, while the application is running in managed mode, data maybe stored according to the first protocol, as described above. While theapplication is running in unmanaged mode, data may be stored accordingto the second protocol, as described above.

In some embodiments, the type and/or location of storage may bedependent on the operation mode in use. For example a storage protocolor policy may specify that data is to be stored in cloud-based storage.The storage protocol or policy may further specify that eitherenterprise or non-enterprise cloud storage should be used, based onoperation mode. When in managed mode, data may be saved to an enterpriseor other cloud storage where a predefined level of security is provided,as selected by the enterprise or policy. Alternatively, when inunmanaged mode, data may be saved or stored in a less secure cloudstorage service or location, e.g., as selected by the user. Illustrativeembodiments may include hybrid storage policies wherein based on certaincircumstances of the mobile device or application, data may be storedlocally when an app is running unmanaged and data may be stored in cloudstorage when the app is running in managed mode, or vice versa.

The process of FIG. 15 may proceed from step 1506 to step 1508, where asignal is received to disable a mode of the application. For example, asignal may be received to disable the managed mode of the application.In an embodiment, device manager 524 may monitor an enrolled mobiledevice, detect a state for the mobile device, and send a signal todisable a managed mode of an application installed on the mobile device.For example, device manager 524 may detect that an enrolled mobiledevice is jailbroken/rooted, and may determine to disable the managedmode of the application based on the detection. In another embodiment,device manager 524 may detect that a black listed application has beeninstalled on an enrolled mobile device, and may determine to disable themanaged mode of the application based on the detection.

In another embodiment, device manager 524 may detect that a managedaccount associated with the application has expired or has been deleted,and may determine to disable the managed mode of the application basedon the detection. For example, a cloud storage application that, whilerunning in managed mode, allows access to secured data may be associatedwith a managed account used to gain access to the secured data. Devicemanager 524 may detect that the managed account has expired or has beendeleted and may send a signal to disable the managed mode of the cloudstorage application based on the detection. In an embodiment, when asignal to disable a managed mode of the application is received, theapplication may be converted into an application that does not run inmanaged mode.

In an embodiment, based on the received signal to disable a managed modeof an application, it may be determined that data stored according to afirst protocol is to be selectively deleted. For example, data storedaccording to a first protocol may be associated with the managed modethat is to be disabled, and the data stored according to the firstprotocol may be selectively deleted as a part of disabling the managedmode.

The process of FIG. 15 may proceed from step 1508 to step 1510, wheredata stored on the mobile device according to a protocol is located. Forexample, device manager 524 may monitor an enrolled mobile device andlocate data that is stored according to a first protocol. The datastored according to the first protocol may comprise data associated witha particular application running in a first mode, such as an applicationrunning in a managed mode. In an embodiment, the located data maycomprise enterprise data for the application.

In an embodiment, the data stored according to the first protocol may belocated based on an account. For example, an account may be associatedwith a managed account. An application may run in managed mode andstored data may be associated with the managed account. In thisembodiment, the data stored according to the first protocol may beassociated with the managed account, and the data stored according tothe first protocol may be located based on the managed account.

In another embodiment, the data stored according to the first protocolmay be located based on a storage container. For example, a securestorage container, such as secure data container 528 of FIG. 5, may beassociated with data stored according to the first protocol. Anapplication may run in managed mode and data stored according to thefirst protocol may be stored in the secure data container. In thisembodiment, the data stored according to the first protocol may bestored in the secure data container, and the data stored according tothe first protocol may be located based on the storage in the securestorage container.

In another embodiment, the data stored according to the first protocolmay be located based on an encryption. For example, data storedaccording to the first protocol may be encrypted using a particularencryption, such as an encryption using a first key. An application mayrun in managed mode and data stored according to the first protocol maybe encrypted based on the particular encryption. In this embodiment, thedata stored according to the first protocol may be located based theencryption for the data. In an example, the first key may be associatedwith device manager 524.

The process of FIG. 15 may proceed from step 1510 to step 1512, wherethe located data is selectively deleted. For example, device manager 524may monitor an enrolled mobile device, locate data stored according tothe first protocol on the enrolled mobile device, and selectively deletethe located data. In an embodiment, selectively deleting the locateddata does not delete any other data stored on the mobile device. Forexample, where the located data comprises enterprise data for anapplication, the personal data for the application might not be deleted.Alternatively, access to data stored according to the first protocol maybe locked or blocked until the device reenrolls or the application iscapable of again running in managed mode.

In FIG. 16, a flowchart of example method steps for managing an accountfor an application capable of executing in multiple modes is shown. Theprocess of FIG. 16 may be used upon detection that an installedapplication is capable of executing in multiple modes to configureaccess to enterprise resources by the application executing in a managedmode. In addition, resources may be pre-provisioned based on certainevents (e.g., a new employee starts with a company, and resources arepre-provisioned as part of the new employee procedures), therebyspeeding up first time execution of managed apps. FIG. 16 may begin atstep 1602, where a mobile device is monitored for new applications. Forexample, device manager 524 may monitor an enrolled mobile device, suchas mobile device 502, as described above. The device manager may monitorthe installed applications on the mobile device. In an embodiment, thedevice manager may periodically monitor the mobile device for theinstallation of new applications.

The process of FIG. 16 may proceed from step 1602 to step 1604, where itis detected that an application capable of running in a managed mode andan unmanaged mode is installed on the mobile device. For example, devicemanager 524 may monitor an enrolled mobile device and determine that anapplication capable of running in a managed mode and an unmanaged modeis installed on the mobile device. The device manager may detect thatthe installed application is capable of running in a managed mode and anunmanaged mode based on meta-data associated with the application orbased on any other suitable detection manner.

The process of FIG. 16 may proceed from step 1604 to step 1606, where aresource is provisioned to communicate with the detected application.For example, a resource, such as a gateway server (e.g., gateway server560) may be provisioned to communicate with the detected applicationwhen the application is running in managed mode.

In an embodiment, the resource may comprise a cloud storage resource.The cloud storage resource may store secure data, such as enterprisedata. In this example, the cloud storage resource may be provisioned tocommunicate with the detected application running in managed mode suchthat the detected application running in managed mode may access thesecure data stored in the cloud storage resource after provisioning.

In an embodiment, provisioning the resource may comprise creating anaccount for the application. In such an embodiment, the process of FIG.16 may proceed from step 1604 to step 1606, where an account is createdfor the application that is associated with identification informationfrom the mobile device. For example, an enrolled mobile device may haveidentification information associated with the mobile device and/orassociated with a user of the mobile device. In an embodiment, theidentification information may comprise an enterprise credential, suchas a login and password for an active directory for an enterprise. Inanother embodiment, the identification information may comprise a tokenassociated with an enterprise. For example, an enrolled mobile devicemay receive a token, such as a Security Assertion Markup Language (SAML)token or any other suitable token, from an enterprise server thatidentifies the enrolled mobile device and/or a user for the enrolledmobile device. The identification information may comprise any othersuitable identification information. The device manager (e.g., devicemanager 524) may access the identification on the mobile device, such asa token, or the mobile device may provide the identificationinformation.

In an embodiment, an account may be created for the application capableof executing in managed mode and unmanaged mode that is associated withthe identification information. In this example, the identificationinformation may comprise user credentials, for example enterprisecredentials, a token, or any other suitable identification information.In an embodiment, an account may be created based on a determinationthat an account associated with the identification information does notalready exist for the application. For example, a server may search foran account for the application based on the identification informationand an account may be created based on the server failing to find anaccount.

In an embodiment, the created account may be associated with theresource being configured to communicate with the application running inmanaged mode. For example, a created account may be associated with acloud storage resource being configured to communicate with theapplication running in managed mode may.

The process of FIG. 16 may proceed from step 1606 to step 1608, where anaccount may be identified based on the identification information. Forexample, an account for a user, such as a user associated with anenterprise, may be identified based on the identification information,such as credentials for the user. The identified account may comprise anenterprise active directory account, an account affiliated withenterprise resource rights, or any other suitable enterprise account. Inan embodiment, enterprise resources may be accessed on an enrolledmobile device by signing onto to the identified accounts, as describedabove.

The process of FIG. 16 may proceed from step 1608 to step 1610, wherethe created account may be linked with the identified account. Forexample, an account created for an application capable of running inmanaged mode and unmanaged mode may be linked with an enterpriseaccount, such as an active directory account. Using the link, theapplication running in managed mode may be able to access systemresources based on access rights for the identified account. Forexample, where the resource being configured to communicate with theapplication running in managed mode comprises a cloud storage resource,the application running in managed mode may access secure data in thecloud storage resourced based on the link.

In an embodiment, after an account is created for the applicationcapable of running in managed mode according to FIG. 16, the applicationmay access secure data based on the created account. For example, a usermay login to the created account using the application running inmanaged mode and credentials for the user, such as a login and passwordor a token. A server, such as gateway server 560, may permit theapplication running in managed mode to login to the created accountbased on the provided credentials for the user. The application mayrequest access to enterprise data, such as email for the user or securedocuments. The server may permit access to the application based on thelinked account. For example, the linked account may comprise an activedirectory account and/or an account that comprises access rights for theuser. The application may be permitted to access enterprise dataaccording to access rights comprises in the linked account.

In an embodiment, the application may comprise a bring your ownapplication and device manager 524 may alter and/or configure theapplication. For example, the alteration and/or configuration maycomprise adjusting the application such that the application may be runin managed mode. For instance, an application may be altered and/orconfigured such that the data stored by the application while it isrunning in managed mode is encrypted or is stored in a secure datacontainer. In another example, an application may be altered and/orconfigured such that the application while it is running in managed modemay communicate with one or more secure resources (e.g., gateway server560). In this example, the secure resource may comprise a cloud storageresource that has been provisioned to communicate with the applicationrunning in managed mode, as described above.

In an embodiment, an application store may provide an applicationcapable of being executed in multiple operations modes. An applicationstore may provide downloadable applications to mobile devices. Forexample, a mobile device may request a list of downloadableapplications, and the application store may provide the requested list.The mobile device may then download one of the listed applications fromthe application store and install the downloaded application.

In an embodiment, an application store may provide a plurality ofversions of an application and may provide a version that is capable ofrunning in multiple operation modes. For example, an application storemay provide a version of an application that is capable of running inmanaged mode or unmanaged mode, as described above.

In FIG. 17, a flowchart of example method steps for providing adownloadable application capable of executing in multiple modes is shownaccording to an embodiment. FIG. 17 may begin at step 1702, where arequest is received for downloadable applications. For example, a mobiledevice, such as mobile device 502, may request a list of downloadableapplications from the application store.

The process of FIG. 17 may proceed from step 1702 to step 1704, where itis determined whether the mobile device is configured to execute anapplication in multiple modes. For example, it may be determined whetherthe mobile device is configured to execute an application in managedmode and in unmanaged mode.

In an embodiment, it may be determined whether the mobile device isconfigured with an application management framework capable of executingan application in managed mode and unmanaged mode. It may be determinedwhether the mobile device is configured with an application managementframework such as application management framework 614.

In an embodiment, determining whether the mobile device is configuredwith an application management framework capable of executing anapplication in managed mode and unmanaged mode may comprise detectingthat a managed application associated with an application managementframework is installed on the mobile device. For example, it may bedetected whether a managed application, such as client agent 604, thatis associated with an application management framework, such asapplication management framework 614, is installed on the mobile device.Detecting that an application such as client agent 604 is installed onthe mobile device may allow a determination that the mobile device isconfigured with an application management framework capable of executingan application in managed mode and unmanaged mode.

In an embodiment, determining whether the mobile device is configuredwith an application management framework capable of executing anapplication in managed mode and unmanaged mode may comprise detectingthat the mobile device is managed by a device manager associated withthe application management framework. For example, it may be detectedwhether a device manager, such as device manager 524, that is associatedwith an application management framework, such as application managementframework 614, manages the mobile device. Detecting that a devicemanager such as device manager 524 manages the mobile device may allow adetermination that the mobile device is configured with an applicationmanagement framework capable of executing an application in managed modeand unmanaged mode.

The process of FIG. 17 may proceed from step 1704 to step 1706, where alist of downloadable applications may be sent to the mobile device basedon the determining. For example, when the mobile device is determined tobe configured with an application management framework that is capableof executing an application in managed mode and unmanaged mode, a listof downloadable applications may be provided that includes a firstversion of an application executable in both managed mode and unmanagedmode. In another example, when the mobile device is determined not to beconfigured with an application management framework that is capable ofexecuting an application in managed mode and unmanaged mode, a list ofdownloadable applications may be provided that excludes the firstversion of an application executable in both managed mode and unmanagedmode. For instance, the application may comprise a file sharingapplication and a first version of the file sharing application maycomprise an application that is executable in both managed mode andunmanaged mode, as described above.

In an embodiment, the first version of the application executable inboth managed mode and unmanaged mode may be associated with theapplication management framework on the mobile device, such asapplication management framework 614. The first version of theapplication may be selected based on the association with theapplication management framework implemented by the mobile device. Forexample, the application store may comprise a plurality of versions ofthe application executable in managed mode and unmanaged mode, and thefirst version of the application may be selected for listing because thefirst version is configured for execution and/or management by theapplication management framework. By selecting the appropriate versionof an application based on the application management framework of agiven mobile device, a single application store may provide applicationsto a wide array of mobile devices regardless of the applicationmanagement framework implemented by a device. As such, each applicationmanagement framework provider need not maintain a dedicate applicationstore and application developers can simply supply one or more versionsof an application to a single application store for distribution.

In an embodiment, the first version of the application executable inboth unmanaged mode and managed mode may be associated with a devicemanager that manages the mobile device, such as device manager 524. Thefirst version of the application may be selected based on theassociation with the device manager. For example, the application storemay comprise a plurality of versions of the application executable inmanaged mode and unmanaged mode, and the first version of theapplication may be selected for listing based on an association with thedevice manager that manages the mobile device.

In an embodiment, based on the list of downloadable applications, themobile device may download and install an application. For example, inan embodiment where the list comprises a version of an applicationexecutable in managed mode and unmanaged mode, the mobile may downloadthe version of the application and install the version of theapplication. The mobile device may then execute the installedapplication in managed mode or in unmanaged mode.

In another embodiment, an application installed on an enrolled mobiledevice may comprise an external application. For example, an enrolledmobile device may receive an application from an external sourceunaffiliated with a device manager for the mobile device (e.g., devicemanger 524), such as a general application store, rather than anenterprise source affiliated with a device manager for the enrolledmobile device (e.g. device manager 524), such as an enterpriseapplication store. In an embodiment, the external application maycomprise a general application that is not associated with an enterpriseapplication store.

In an embodiment, the external application may request to sign on to anenterprise account and/or an enterprise server. An enterprise accountmay comprise an account associated with an enterprise, such as anaccount associated with an active directory for an enterprise. Forexample, the external application may comprise an email client, and theemail client may request to sign on to an enterprise email account. Inanother example, the external application may comprise a cloud storageapplication, and the cloud storage application may request to sign on toa server that allows access to enterprise resources, such as a gatewayserver.

In an embodiment, an enrolled mobile device, such as enrolled mobiledevice 502 of FIG. 5, may have an external application installed, andthe external application may submit a request to a server, such asgateway server 560 of FIG. 5, to access an enterprise account. This maycomprise an example of a bring your own application (BYOA) embodiment.

In an embodiment, a bring your own application installed on a managedmobile device may be altered and/or configured by a device managermanaging the mobile device. For example, a bring your own applicationinstalled on mobile device 502 may be altered by device manager 524. Thealteration and/or configuration may comprise adjusting the applicationsuch that the application may be run in managed mode. For instance, anapplication may be altered and/or configured such that the data storedby the application while it is running in managed mode is encrypted oris stored in a secure data container. In another example, an applicationmay be altered and/or configured such that the application while it isrunning in managed mode may communicate with one or more secureresources (e.g., gateway server 560).

Although the subject matter has been described in language specific tostructural features and/or methodological acts, it is to be understoodthat the subject matter defined in the appended claims is notnecessarily limited to the specific features or acts described above.Rather, the specific features and acts described above are described asexample implementations of the following claims, and other embodimentsmay be practiced. For example, various other embodiments include, butare not limited to, the following.

One embodiment may include a method comprising: running, on a mobiledevice, an application in a first mode, wherein the first mode is amanaged mode; running, on the mobile device, the application in a secondmode, wherein the second mode is an unmanaged mode, wherein saidapplication is running in the second mode at a mutually exclusive timefrom when said application is running in the first mode; receiving arequest to store data associated with the application; storing the dataaccording to a first protocol when the application is running in themanaged mode and storing the data according to a second protocol whenthe application is running in the unmanaged mode. In such an embodiment,the first protocol may comprise storing data in a first data containerand the second protocol may comprise storing data in a second datacontainer mutually exclusive from the first data container. Such anembodiment may further comprise restricting the application fromaccessing the first data container when running in the unmanaged mode.Such an embodiment may further include the first protocol comprisingencrypting data with a first key prior to storing that data and thesecond protocol comprising at least one of encrypting data with a secondkey prior to storing the data and storing data unencrypted. In somecases, the application running in the managed mode is managed by adevice manager in accordance with one or more policy files separate fromthe application and applicable to a plurality of applications. Someaspects may also include receiving a signal from the device manager todisable the managed mode of the application. When that happens, theembodiment may locate, in response to the received signal, data storedaccording to the first protocol, and selectively delete the locateddata. Locating the data stored according to the first protocol mayinclude determining a managed account associated with the application,and locating the data based on the managed account. In some cases,locating data stored according to the first protocol further compriseslocating a container that stores data according to the first protocol.In some aspects, locating data stored according to the first protocolfurther comprises determining an encryption key associated with thefirst protocol; and locating the data based on the determined encryptionkey. In some embodiment, the device manager disables the managed mode inresponse to identifying a black listed application installed on themobile device. The device manager may disable the managed mode inresponse to detecting that a managed account associated with theapplication has expired. The device manager may disable the managed modein response to detecting that the mobile device has been jailbroken orrooted. In some cases, selectively deleting the located data does notdelete personal data associated with the application stored on themobile device.

Another embodiment may include a computing device comprising aprocessor, wherein the computing device is configured to run anapplication in a first mode, wherein the first mode is a managed modeoperating under the control of one or more policy files separate fromthe application and usable to manage operations of multiple applicationsexecuting on the computing device; run the application in a second mode,wherein said application is running in the second mode at a mutuallyexclusive time from when said application is running in the first mode;receive a request to store data associated with the application; andstore the data according to a first protocol when the application isrunning in the first mode and store the data according to a secondprotocol when the application is running in the second mode. In someaspect the first protocol comprises storing data in a first datacontainer and the second protocol comprises storing data in a seconddata container different from the first data container. In someembodiments the computing device is further configured to restrict theapplication from accessing the first data container when running in thesecond mode. In some embodiments the first protocol comprises encryptingdata with a first key prior to storing that data and the second protocolcomprises at least one of encrypting data with a second key prior tostoring the data and storing data unencrypted. In some embodiments thefirst mode is a first managed mode, and the second mode is a secondmanaged mode managed in accordance with at least one different policyfile than the first managed mode.

Yet another embodiment may include one or more non-transitorycomputer-readable storage media storing computer-executable instructionsthat, when executed by one or more processors of a data processingsystem, cause the system to: run an application in a first mode, whereinthe first mode is a managed mode; run the application in a second mode,wherein the second mode is an unmanaged mode, wherein said applicationis running in the second mode at a mutually exclusive time from whensaid application is running in the first mode; receive a request tostore data associated with the application; store the data according toa first protocol when the application is running in the managed mode andstore the data according to a second protocol when the application isrunning in the unmanaged mode.

In another illustrative embodiment, a method may include periodicallymonitoring a mobile device to determine that a new software applicationis installed on the mobile device; detecting that the application iscapable of running in both a first mode and a second mode, wherein thefirst mode is a managed mode operating under the control of one or morepolicy files separate from the application and usable to manageoperations of multiple applications executing on the computing device;provisioning a resource to communicate with the application such thatthe resource is configured only to communicate with the application whenthe application is running in the first mode, and not to communicatewith the application when the application is running in the second mode.In some aspects the resource comprises a cloud storage resource thatstores secure data. In some aspects provisioning the resource comprisesprovisioning the cloud data storage resource to allow the application toaccess secure data stored in the cloud data storage resource while theapplication is running in the first mode. In some aspects the mobiledevice is managed by a device manager, and wherein the device manageradministers the one or more policy files. In some aspects provisioningthe resource further comprises creating an account with the resource forthe application associated with identification information from themobile device; locating a managed account based on the identificationinformation; and linking the managed account to the created account. Insome aspects the second mode is a second managed mode operating underthe control of one or more policy files different from the first mode.In some aspects the first mode is associated with a first user role, andthe second mode is associated with a second user role different from thefirst user role. In some aspects the first mode is associated with afirst workplace environment type, and the second mode is associated witha second workplace environment type. In some aspects the method includesdetecting that the application is running in the first mode; andallowing the application to access secure data based on the createdaccount. In some aspects the method includes receiving a request fromthe application running in the first mode, wherein the request comprisesa request to access secure data; and granting the application access tothe secure data based on the created account. In some aspects theapplication is distributed by an enterprise to the device.

In another illustrative embodiment, a device with a processor isconfigured to: periodically monitor a mobile device to determine that anew software application is installed on the mobile device; detect thatthe application is capable of running in both a first mode and a secondmode, wherein the first mode is a managed mode operating under thecontrol of one or more policy files separate from the application andusable to manage operations of multiple applications executing on thecomputing device; provision a resource to communicate with theapplication such that the resource is configured only to communicatewith the application when the application is running in the first mode,and not to communicate with the application when the application isrunning in the second mode. In some aspects, the resource comprises acloud storage resource that stores secure data. In some aspectsprovisioning the resource comprises provisioning the cloud data storageresource to allow the application to access secure data stored in thecloud data storage resource while the application is running in thefirst mode. In some aspects the mobile device is managed by a devicemanager, wherein the device manager administers the one or more policyfiles. In some aspects provisioning the resource further comprises:creating an account with the resource for the application associatedwith identification information from the mobile device; locating amanaged account based on the identification information; and linking themanaged account to the created account. In some aspects the second modeis a second managed mode operating under the control of one or morepolicy files different from the first mode. In some aspects the firstmode is associated with a first user role, and the second mode isassociated with a second user role. In some aspects the device furtheris configured to: detect that the application is running in the firstmode; and allow the application to access secure data based on thecreated account.

In another illustrative embodiment, one or more non-transitorycomputer-readable storage media store computer-executable instructionsthat, when executed by one or more processors of a data processingsystem, cause the system to perform: periodically monitoring a mobiledevice to determine that a new software application is installed on themobile device; detecting that the application is capable of running inboth a first mode and a second mode, wherein the first mode is a managedmode operating under the control of one or more policy files separatefrom the application and usable to manage operations of multipleapplications executing on the computing device; and provisioning aresource to communicate with the application such that the resource isconfigured only to communicate with the application when the applicationis running in the first mode, and not to communicate with theapplication when the application is running in the second mode.

The invention claimed is:
 1. A method comprising: providing, by a mobiledevice, an application, the application including a first mode and asecond mode, the first mode and the second mode being a managed modemanaged by a device manager in accordance with one or more policy filesseparate from the application and applicable to a plurality ofapplications, and the second mode being executable at a mutuallyexclusive time of the first mode; creating, by the mobile device, anaccount associated with a user of the application; linking, by themobile device, the account to a first managed account with theapplication in the first mode; linking, by the mobile device, theaccount to a second managed account with the application in the secondmode, wherein the first managed account has access to data storedaccording to a first protocol, and the second managed account has accessto data stored according to a second protocol; receiving, by the mobiledevice, a request to store data associated with the application; andstoring, by the mobile device, the data with the application in thefirst mode according to the first protocol and with the application inthe second mode according to the second protocol.
 2. The method of claim1, wherein the first protocol comprises storing data in a first datacontainer and the second protocol comprises storing data in a seconddata container mutually exclusive from the first data container.
 3. Themethod of claim 2, further comprising restricting the application fromaccessing the first data container when running in the second mode. 4.The method of claim 1, further comprising locating data according to thefirst protocol by locating data stored according to the first protocolcomprises: determining a managed account associated with theapplication; and locating the data based on the managed account.
 5. Themethod of claim 1, further comprising locating data according to thefirst protocol by locating data stored according to the first protocoland locating a container that stores data according to the firstprotocol.
 6. The method of claim 1, further comprising locating the datastored according to the first protocol by: encrypting the data with afirst key prior to storage of the data according to the first protocol;determining the first key associated with the first protocol; andlocating the data based on the determined first key.
 7. The method ofclaim 1, further comprising: disabling the first mode in response toidentifying a black listed application installed on the mobile device.8. The method of claim 1, further comprising: disabling the first modein response to detecting that a managed account associated with theapplication has expired.
 9. The method of claim 1, further comprising:disabling the first mode in response to detecting that the mobile devicehas been jailbroken or rooted.
 10. A method of claim 1, furthercomprising: selectively deleting the data stored on the mobile deviceassociated with the first protocol upon receiving a signal to disablethe first mode of the application.
 11. A computing device comprising: aprocessor, wherein the computing device is configured to: provide anapplication in a first mode and a second mode, the first mode and thesecond mode being a managed mode managed by a device manager inaccordance with one or more policy files separate from the applicationand usable to manage operations of multiple applications executing onthe computing device, and the second mode being executable at a mutuallyexclusive time of the first mode; create an account associated with auser of the application; link the account to a first managed accountwith the application in the first mode; link the account to a secondmanaged account with the application in the second mode, wherein thefirst managed account has access to data stored according to a firstprotocol, and the second managed account has access to data storedaccording to a second protocol; receive a request to store dataassociated with the application; and store the data with the applicationin the first mode according to the first protocol and with theapplication in the second mode according to the second protocol.
 12. Thecomputing device of claim 11, wherein the first protocol comprisesstoring data in a first data container and the second protocol comprisesstoring data in a second data container different from the first datacontainer.
 13. The computing device of claim 11, wherein the computingdevice is further configured to: restrict the application from accessingthe first data container when running in the second mode.
 14. Thecomputing device of claim 11, wherein the first mode is a first managedmode, and the second mode is a second managed mode managed in accordancewith at least one different policy file than the first managed mode. 15.The computing device of claim 11, wherein the computing device isfurther configured to: determine a managed account associated with theapplication; and locate the data based on the managed account.
 16. Thecomputing device of claim 11, wherein the computing device is furtherconfigured to locate data stored according to the first protocol bylocating a container that stores data according to the first protocol.17. The computing device of claim 11, wherein the computing device isfurther configured to locate the data stored according to the firstprotocol by: encrypting the data with a first key prior to storage ofthe data according to the first protocol; determining the first keyassociated with the first protocol; and locating the data based on thedetermined first key.
 18. One or more non-transitory computer-readablestorage media storing computer-executable instructions that, whenexecuted by one or more processors of a data processing system,configure the system to: provide an application in a first mode and asecond mode, the first mode and the second mode being managed modemanaged by a device manager in accordance with one or more policy filesseparate from the application and usable to manage operations of aplurality of applications, and the second mode being executable at amutually exclusive time of the first mode; create an account associatedwith a user of the application; link the account to a first managedaccount with the application in the first mode; link the account to asecond managed account with the application in the second mode, whereinthe first managed account has access to data stored according to a firstprotocol, and the second managed account has access to data storedaccording to a second protocol; receive a request to store dataassociated with the application; and store the data with the applicationin the first mode according to the first protocol and with theapplication in the second mode according to the second protocol.